Well, historically on MS Windows, the support and resources folders were beneath the binary (program/app) folders.
This was not where either platform (OSX & MS Windows) intended for application or user data to be located.
But mostly on Windows platform there was a long standing issue with Unicode string pathnames not being supported by Ruby version in the 1.8 trunk, which was SketchUp version up through v2013. (OSX had always natively supported Unicode strings and paths.)
So, in 2013 and earlier, on Windows, all the folders were in the program folder paths.
On Mac, up through v8, the
"Plugins" were in
"Macintosh HD/Library/Application Support/SketchUp".
For v2013, the
"Plugins" folder moved to:
"~/Library/Application Support/SketchUp 2013/SketchUp".
(These facts come from the Release Notes Page.)
Unicode pathname support for Windows was finally solved with the release of SketchUp 2014 which upgraded it’s embedded Ruby version to 2.0.0-p247 and also included the Ruby Standard Library for the first time.
Also with this 2014 version, the Trimble development team began migrating user data folders out of the program (binary) path into AppData paths where they belonged. (There were permissions issues with installing plugins and files in general into the program files paths with Windows Vista and later for security reasons.)
So the first year of Ruby 2, SketchUp 2014 implemented
"Classifications" in the user AppData path.
The second year, SketchUp 2015 implemented a 64-bit edition for Windows, and that one had a
"Gems64" folder. Otherwise they were the same 3 folders for the 32-bit edition.
The third year of Ruby 2.0, SketchUp 2016 remained the same as the previous year.
The 4th year, Ruby was updated to 2.2.4, and SketchUp 2017 no longer had a 32-bit WIndows build, so the gems folders are all named
On Windows, they moved the default content that comes with SketchUp (
"Styles") out of the Program Files directory and placed them in the ProgramData directory.
In addition they implemented user
It seems like a table would be a nice addition to the documentation for file locations.
Because that is what they were originally named, and their name was changed in the GUI interface and help files, but there was not a good reason to change the class name. I generally refer to them as “scene pages” to cover both names.