[Request] A dedicated NURBS workbench

[Kunda1]

+ we definitely could us a cplusplus dev or more to translate some of these awesome python NURBS based code to speed up their execution.

Edit: @JeffWitz would you be interested in making a chart comparison ? That way we can grok where each workbench is at?

[Cekuhnen]

Very interesting topic

Two thoughts:

1 tool amount
comparing rhino and Fusion360 is very interesting for sketching and surface modeling

Today I don’t miss the shear amount of tools rhino has because I can build all I need with fusion and I do product design
Jewelry is a different question

Fusion is a good example of less is more and rhino is a good example of making it needlessly complex

The surface modeling from fusion 360 is a really good example to show few rooms one only effectively needs
Extrude sweep revolve fill loft while loft In fusion includes many tasks for which rhino had each dedicated single tools


2 c++ code vs python
Some tools in popular workbenches are as far as I know made in python and I see this already as a show stopper for me with basic test models.

This can be a chicken or egg question. I think if auch tools are faster more users would come and use it.


The curve WB is a great example die fantastic tools but then the speed is a show stopper.


Clarify:

Surface and curve WB to me should be joined and expanded
And part WB already delivers the foundation for basic tools
Like sweep loft and extrude while I feel loft in part WB should be able to have g1 G2 blend abilities

Or all this is part of the surface curve WB

A further development of nurbs / surface modeling would seriously help freecad being more useable for product design.
Currently it lacks too much and is to slow / unstable to be seriously considered in that area - despite some cool modeling video on YouTube.

[onekk]

There were some discussion about editing Nurbs in:

https://forum.freecadweb.org/viewtopic.php?f=3&t=16473

And maybe some work is already done somewhere.

I will be pleased if there were simply a "unified toolbar" that could group various commands found in "curves" "nurbs" silk and other workbenches, and I will be very pleased if there will be some efforts to "unify" some of this tools in an unique WB or even directly in the Part module.

Regards

Carlo D.

[Pauvres_honteux]

@JeffWitz

Hi Kunda1, perhaps you could split off the posts from and including JeffWitz thread till this post and link it back to this thread?
Reason being this thread was supposed to be a link collector of discussions.

[Kunda1]

@JeffWitz

Hi Kunda1, perhaps you could split off the posts from and including JeffWitz thread till this post and link it back to this thread?
Reason being this thread was supposed to be a link collector of discussions.

Done:
Discussion: numba jit nopython (@njit) allows to reduce process time and works quite well with numpy.
https://forum.freecadweb.org/viewtopic.php?f=8&t=61045

[Pauvres_honteux]

Done:
Discussion: numba jit nopython (@njit) ...

Brilliant Kunda1 !
I take it you will also remove the same stuff from this thread as well?

[Kunda1]

I take it you will also remove the same stuff from this thread as well?

give me a heads up if I don't

[mariwan]

I really wish to be able to fix all the issues still exist in the Nurbs WB of Microlley that I modified.
But, my WB is prioritized over the Nurbs WB. For two reasons:
1-I need to learn more how things work in FreeCAD/COIN/..etc to fix his code.
2-I wish to do as much as I can for my WB before working again with the Nurbs. I wish that other developers will be interested in my WB and wish to get some more developers involved with me.
Unfortunately, as many others developers here, my time is limited.

Regarding converting python code to cpp: I believe if we have a functional code in python, it shouldn't be too difficult to convert it to cpp. I would help in that but just not now.

[Pauvres_honteux]

I really wish to be able to fix all ...

Please don't work so hard you end up like microelly2, with your body firmly planted in the infamous wall.
And we DO REALLY APPRECIATE your extravagantly hard work!
Don't ever forget the soul soothing forrest promenad!

I wish ... more developers involved ...

We fully agree on that one!

... converting python code to cpp: ... it shouldn't be too difficult ...

Sounds promising! Perhaps a reciepe for future general development? The script kiddies put together something. Later on the C-girls/-guys tidy it up to make it blistering fast?