Let us say one wants to create component and/or pattern libraries and distribute to others for use (eg put them on github), and for others to periodically update them.
But how portable are the libraries?
Is it enough to give the component library with the pattern already assigned (in other words, is the pattern copied into the component library when it's assigned to a component?), or does both the component library and the library holding the pattern it uses have to be distributed?
What about 3d models, I don't think they are copied into the library when assigned to a pattern, and looking at the library file it appears to hard-code paths, so those exact same paths and models would have to be present on the "destination" machine?
Is there a better way to do this?
Portability of libraries
Re: Portability of libraries
Component library includes all attached patterns. One may distribute component library only. But 3D model files are much bigger that library files therefore 3D models are not included in library. It has paths to 3D models only. A distributor can edit paths to 3D models and save 3D model file names instead full paths. It is easy to do in ASCII format (export ASCII file from DipTrace, edit ASCII file in text editor, save it and import modified ASCII file in DipTrace). DipTrace can find models by name. User should specify search path (Tools->3D Preivew->Patterns and Models Seach->Add) and program will find 3D models on local machine.