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.
FS Node Studio beta.
Konst_Sh
Member Posts: 72 PRO
Today within the set of other free Onshape automation tools by CadSharp we releasing in Onshape Appstore the beta version of unique tool for visual and interactive creation of Onshape's Custom features code - FS Node Studio.
It aims to abstracts away the most cryptic parts of Featurescript functions - the id's manipulation, and represents each function instance - the building block of your custom feature - as a diagram node with inputs, outputs and the links connecting outputs/results of functions with inputs of other descendant functions.
It has a special grouping constructs to represent well known code statements like if-else, try-catch, for loop, and embedable raw code fragment. It enforces type safety of passed values by checking type matching of source values and consumer argument type, so type annotations are your friends not just at runtime 😏 (but not be afraid, the unchecable Any parameter type will let you bypass type checks as we used to) . The tool has full publicly documented Onshape standard library set of functions and types.
The tool is capable to generate full FeatureStudio declaration code including custom types, enums, top level functions and custom features, except the import statements and FeatureScript version directive.
Also the current limitation is that you will not be able to save you diagram within Onshape tab and you will need to manually copy code from featurescript output of the app to FeatureStudio tab.
Introductory video by @MichaelPascoe
Comments
"you will not be able to save you diagram within Onshape tab"
This is confusing, since the demo video seems to show step by step editing of the node graph where it persists. What exactly do you mean?
Simon Gatrall | Product Development Specialist | Open For Work
Wow! That looks like an awful lot of work, and an amazing tool. Thank you for sharing.
I had a lot of fun testing it out and the idea of visual scripting is very appealing.
Probably especially appealing for non-developers I imagine.
This is actually what I thought FeatureScript was way back in the day when I read "you don't need to know how to code in order to do FeatureScript".
Way to go @Konst_Sh! This is super cool. 😎
@S1mon You can open FS Node Studio (BETA) from the app menu (Bottom left +) then when finished copy your code over to a Feature Studio. However, currently it is not saving the data anywhere. So if you close your browser tab and open it again, your data will not be saved unless you have copied it over to a Feature Studio.
Here is the forum post for the toolbox app:
CADSharp Toolbox App
.
FYI: We will post other individual pages for the other sub apps. This way you can follow along as they are updated like with Konstantin's FS Node Studio (BETA)
.
Learn more about the Gospel of Christ ( Here )
CADSharp - We make custom features and integrated Onshape apps! Learn How to FeatureScript Here 🔴
I mean the tab within onshape document, the own app tabs will persist while the user session is retained, but if you close it or refresh - it will not be saved.
Is this something that needs changes from Onshape to allow the tab to be persistent between sessions? Or would there be a way to add comments or other stuff to the generated code to allow it to become the storage medium?
Simon Gatrall | Product Development Specialist | Open For Work
nope, thats the matter of maturity of my data model. While it is still subjected to changes I don't want to handle possible conflicts of stored json and relevant data model. Another consideration is that i would like to check user interest before making farther efforts of integration it into OS.