Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Version Naming Conventions
NeilCooke
Moderator, Onshape Employees Posts: 5,683
Hi fellow FeatureScripters!
As you know, it can be a difficult task to find the original document that a custom feature was created in so you can add it to your toolbar. With so many copies of each document flying around, it can look something like this:
However, if you name your versions they stand out a little better - in the image above I have prefixed each version with "Official" or "Original". Any ideas for a better naming convention?
Also, it is worth renaming "Main" to "Official" for when searching for a document from the documents page. Open to suggestions if anybody has a better idea?
Thanks.
As you know, it can be a difficult task to find the original document that a custom feature was created in so you can add it to your toolbar. With so many copies of each document flying around, it can look something like this:
However, if you name your versions they stand out a little better - in the image above I have prefixed each version with "Official" or "Original". Any ideas for a better naming convention?
Also, it is worth renaming "Main" to "Official" for when searching for a document from the documents page. Open to suggestions if anybody has a better idea?
Thanks.
Senior Director, Technical Services, EMEAI
3
Comments
Cheers, Owen.
HWM-Water Ltd
What about automatically marking all copies and give option to search/view only originals?
HWM-Water Ltd
Sorting search by links/copies would help, but really a more Github-like "fork/modify/pull request" workflow (where you can also follow links from forked copy to parent to find the original) would solve this both for FeatureScripts and geometry public documents.
PhD, Mechanical Engineering, Stanford University
HWM-Water Ltd