This is the pre-alpha/alpha release of a new CAD that I created. It uses OpenCascade 7.9 under the hood via WASM and a custom sketch solver written in typescript (substantially faster than I thought it would be)
Right now it can do most of the CAD stuff that one expects apart from anything that involves meshes or curved face manipulation - that'll come soon but I want to have a stable base first before I move any further
I hope you like it, I'm eager to hear your thoughts!
Will this project eventually be able to completely replace MechE software students need to use for classes or what is the intentions about your software’s scope
the target audience (which I'm a part off too) is hobbyist and small shops. Competing with the big giants I think is impossible (SolidWorks/Fusion/onShape/etc.) but I think that the vast majority of people use only a very small subset of features
Interoperability is of paramount importance and it's probably going to be the best deep dive
that was the idea and this is such a huge project that I kept as much variables static as possible. I want the app to feel close to what people already know - and that applies to me as a user too (I want to use the app too after all!)
Good job. How long did it take you to build it?
This is the pre-alpha/alpha release of a new CAD that I created. It uses OpenCascade 7.9 under the hood via WASM and a custom sketch solver written in typescript (substantially faster than I thought it would be)
Right now it can do most of the CAD stuff that one expects apart from anything that involves meshes or curved face manipulation - that'll come soon but I want to have a stable base first before I move any further
I hope you like it, I'm eager to hear your thoughts!
Will this project eventually be able to completely replace MechE software students need to use for classes or what is the intentions about your software’s scope
the target audience (which I'm a part off too) is hobbyist and small shops. Competing with the big giants I think is impossible (SolidWorks/Fusion/onShape/etc.) but I think that the vast majority of people use only a very small subset of features
Interoperability is of paramount importance and it's probably going to be the best deep dive
err.. seems like many of the UI elements taken straight from OnShape?
https://www.onshape.com
It's vibe coded, so not surprising that it replicates the patterns of existing systems.
UI is a great place NOT to reinvent things that don't need to be reinvented. Rip off the best and forget the rest.
Whether OnShape is the "best" or not, I have no idea, but the point stands.
that was the idea and this is such a huge project that I kept as much variables static as possible. I want the app to feel close to what people already know - and that applies to me as a user too (I want to use the app too after all!)