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.
Feature Script library is a mess
brett_sutton
Member Posts: 43 ✭✭✭
So I just went looking for a feature script that I had read about (Pocket Holes).
So I did a search for pocket hole and came up with more than 20 results.
There is no way to identify the script by the original author, not to work out which might be the definitive edition.
I've had this problem before and to be honest it makes feature script close to useless as its almost impossible to find the 'working' version of a script.
There are couple of things that need to be done to 1) improve the current situation 2) fix the problem permanantly.
1) add the following to search
Display the author name of the script.
Display the no. of Documents using the script
Display the date the script was last updated.
It would also be a good idea to make the author name searchable.
2) The real fix here is to support the 'forking' and 'pull request' features that github utilise.
With github its always easy to determine what is the definitive version of a project. Even if there are competing versions its pretty clear what the major versions do and how active they are.
The forking and pull request idea also fixes your current problem with public documents. Again we are seeing dozens (hundreds) of copies of a document with no way to see which is the definitive edition.
Pull/forking also allows the whole community to collectively improve a feature script which will benefit everyone.
Feature script and public documents are both powerful featues of onshape but unless you fix the core problem of 'copy hell' they well be only marginally useful.
So I did a search for pocket hole and came up with more than 20 results.
There is no way to identify the script by the original author, not to work out which might be the definitive edition.
I've had this problem before and to be honest it makes feature script close to useless as its almost impossible to find the 'working' version of a script.
There are couple of things that need to be done to 1) improve the current situation 2) fix the problem permanantly.
1) add the following to search
Display the author name of the script.
Display the no. of Documents using the script
Display the date the script was last updated.
It would also be a good idea to make the author name searchable.
2) The real fix here is to support the 'forking' and 'pull request' features that github utilise.
With github its always easy to determine what is the definitive version of a project. Even if there are competing versions its pretty clear what the major versions do and how active they are.
The forking and pull request idea also fixes your current problem with public documents. Again we are seeing dozens (hundreds) of copies of a document with no way to see which is the definitive edition.
Pull/forking also allows the whole community to collectively improve a feature script which will benefit everyone.
Feature script and public documents are both powerful featues of onshape but unless you fix the core problem of 'copy hell' they well be only marginally useful.
Tagged:
6
Comments
For featurescript, when you add a custom feature to your toolbar, use the featurescript samples filter to find the original.
https://www.onshape.com/featurescript
Pocket Holes is listed in the "more" section of the Feature Highlight, so you can just follow the link to the original document and add it directly.
@sjalife
@brett_sutton
You can use https://featurescripts.bubbleapps.io/ to find featurescripts
IR for AS/NZS 1100
There's also this one on improved sorting for public document search.
I can understand public document search being primarily of interest to non-enterprise users, but surely a fork/pull request workflow would be useful for everybody.
PhD, Mechanical Engineering, Stanford University