On Mac I would put them in the User/Application Support/… components folder, on the PC, I use the equivalent in User/App Data/Roaming. Nothing wrong with keeping them in your regular SketchUp file directory, though. Although you don’t need to do it to create the collections, I did make those hidden directories visible. I put my custom materials collections and custom styles in the same location.
As part of my new version migration process I copy those three folders over to the new version in one operation. Note: these are the only folders whose contents get copied to a new version.
For others who might come along looking for this info, don’t put your components, materials, or styles into the the program files. If you every need to reinstall SketchUp, it’ll overwrite the folders and you’ll lose the stuff you’ve added.
Ok, I can see the reasoning for that. That begs for questions about SU versions. Each time you copy your components to the new version’s library, you leave an archive of what you had available to the last version in place and still accessible to it. I’m guessing SU version numbers matter to the component files it makes? While saving a copy of a SU file, you have the option of saving it backwards in versions, but I don’t see any such option when you right click and save a component, but, again I’m guessing: An older version of SU would have trouble with that? I can see if you keep all your components in one place, over time, it will be populated with all different versions, and no obvious way to tell compatibility unless you were disciplined enough to include version numbers in all you file names.
No. There isn’t an option to save as an older version with that save method and yes, older versions would not be able to open components created and saved in a newer version. For me this hasn’t been any issue because once I’ve fully moved into the new version, I’ve not found a reason to go back.
True. And being disciplined would be important if you are regularly going back to older versions. Once I’ve transitioned to the new versions, any components added are added only to the collection in that version of SketchUp. Those components don’t get saved into the older version’s Components collection.
Hi @RTCool,
I have organized the same way, based upon my training and experience. I would say the strongest roots of my SU organizational system are CSI MasterFormat and Architectural Graphic Standards. I then use for LO organization; USNCS and AIA recommendations. I have additionally overlaid ideas from M Brightman, M Donley and N Sonder to tailor my workflow to SketchUp.
That’s been true for me mostly except to support students on a different version, or just to see if there’s a difference in behavior between new and old versions.
So for those cases you’ll obviously need to take extra steps. You could put all your newer components into a fresh SU file and use File>Save as… to save back to the older version and then open that file in the older version and save out the components into the older version collection as above.
Thank you @DaveR for the very detailed description.
Really appreciated.
So, I can create all the components in one Sketchup window and then use ‘Save as Collection’. Is this a one step operation which will add all the components created to a collection. For example, if I have created 10 components in the one model, and then use ‘Save as Collection’, will it add the 10 components to the collection/folder that I create as separate components?
My normal proactive for this is to create a folder in my own location, completely separate from the Sketchup folder. I’m assuming this is ok.
That’s brilliant! Thank you. I was expecting to have to do the Save As 10 times.
So, components, for example in one model, make sure I’ve set the insertion point correct for each one, purge, then ‘Save As Collection’. Sounds good to me.
Curious… what’s the US CSI standard? There is a Standard in the UK, but Architectural firms and Main Contractors tend to butcher it to suit their needs. I work for so many clients that don’t use any standards. I’ve always tried to be really methodical about the way I work. A few years ago, I remember doing a load of work for BAA, (British Aiport Authority), and their file naming standard was still based on the 8 character limit of DOS, and their layer standard in AutoCAD seemed to have no logic to it at all.
MasterFormat is a result of the efforts of CSI and CSC (Constructions Specifications Canada) to create an organizational structure for specifying the materials and methods involved in constructing and maintaining a habitable building. Specifications for building are written instructions from the designer to the contractor and are separate from the Construction Drawings which are drawn instructions from the designer to the contractor. In larger projects Specifications are produced by tradition on 8-1/2" x 11" (A4) paper separate from the Construction Drawings produced on various paper sizes. In smaller projects the Specifications are normally included on the Construction Drawings (usually as Notes).
Back to SU organization. MasterFormat is divided into 50 numbered broad Divisions with each Division having numerous numbered specific Sections. I use several Divisions to describe several different collections of objects in my SU models, Openings being one of them. Wikipedia has a good overview of MasterFormat.
