glider workbench

Show off your FreeCAD projects here!
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Post Reply
User avatar
looo
Veteran
Posts: 3941
Joined: Mon Nov 11, 2013 5:29 pm

glider workbench

Post by looo »

Announcing the glider workbench, a gui for OpenGlider in freecad. Development is still ongoing, but I thought it is time to show the development state. If someone is interested in testing or developing I can give instructions on how to install OpenGlider and this workbench.
Image
User avatar
DeepSOIC
Veteran
Posts: 7896
Joined: Fri Aug 29, 2014 12:45 am
Location: used to be Saint-Petersburg, Russia

Re: glider workbench

Post by DeepSOIC »

Cool!
At the moment, I'm not interested in it, but it' cool anyway. I wonder, how many purpose-specific workbenches are out there.
triplus
Veteran
Posts: 9471
Joined: Mon Dec 12, 2011 4:45 pm

Re: glider workbench

Post by triplus »

Looking good.
jmaustpc
Veteran
Posts: 11207
Joined: Tue Jul 26, 2011 6:28 am
Location: Australia

Re: glider workbench

Post by jmaustpc »

that is really interesting :)
User avatar
yorik
Founder
Posts: 13640
Joined: Tue Feb 17, 2009 9:16 pm
Location: Brussels
Contact:

Re: glider workbench

Post by yorik »

VERY nice looo! The code looks very clean too, congrats
User avatar
looo
Veteran
Posts: 3941
Joined: Mon Nov 11, 2013 5:29 pm

Re: glider workbench

Post by looo »

Thanks for the replies. I will post updates, but the development will take time. And at the moment it isn't sure which front end we will choose. We do not use many things from freecad right now. Mostly the workbench uses pivy and qt. But as I have seen some fem visualisation tools arriving and the latest calculix has announced to support membrane elements, there will be some good things we can use from freecad.

Does anyone know if occ has some functionality to unwrap develop able and non develop able surfaces? This would be another useful tool for us.
User avatar
microelly2
Veteran
Posts: 4688
Joined: Tue Nov 12, 2013 4:06 pm
Contact:

Re: glider workbench

Post by microelly2 »

I have integrated your workbench into the pluginloader
There are some specials I do not understand
import freecad_glider cannot work inside the same directory, to get the path
I have added an empty file freecad_glider.py to the directory freecad_glider
I load this file to get the __file__ variable then I have to load tools .

This is my modified InitGui.py

Code: Select all


    def Initialize(self):
        import tools

        Gui.addCommand('CreateGlider', tools.CreateGlider())


Can you check it for your? If you commit it into your git - the workbench is integrated.
https://github.com/microelly2/freecad-p ... 3e1ee947b7
bn_816.png
bn_816.png (81.71 KiB) Viewed 39036 times
User avatar
looo
Veteran
Posts: 3941
Joined: Mon Nov 11, 2013 5:29 pm

Re: glider workbench

Post by looo »

thanks for your efforts.
import freecad_glider cannot work inside the same directory, to get the path
In my case it is working because I have the freecad_glider directory inside of /usr/lib/freecad/Mod which is in my case part of the sys.path.
but I will change this soon.

As I have already said in another topic, I am not happy with the freecad way to add python modules. I think this has to be fixed. A solution would be to not add every package to the python path, instead only add the base directories (/usr/lib/freecad, /home/.../.FreeCAD/Mod). + changeing the shared objects to _package.so and import them in the __init__.py of the package.
User avatar
microelly2
Veteran
Posts: 4688
Joined: Tue Nov 12, 2013 4:06 pm
Contact:

Re: glider workbench

Post by microelly2 »

looo wrote: As I have already said in another topic, I am not happy with the freecad way to add python modules. I think this has to be fixed. A solution would be to not add every package to the python path, instead only add the base directories (/usr/lib/freecad, /home/.../.FreeCAD/Mod). + changeing the shared objects to _package.so and import them in the __init__.py of the package.
Yes, I agree. As the number of workbenches increases there will come conflicts. My idea was to put the extra modules (macro collections into a subdirectory where I can manager the __init__.py). But for workbenches the users want to have in the workbench list. I think there should be a discussion continued to get a robust redesign that allows the integration of community workbenches with clear defined namespaces.

seems that this is the right place for discussion: viewtopic.php?f=22&t=13238
User avatar
microelly2
Veteran
Posts: 4688
Joined: Tue Nov 12, 2013 4:06 pm
Contact:

Re: glider workbench

Post by microelly2 »

No hurry,
There are still some small problems - see this thread above.
after that finished I post how to get all installed (you need openglider too)
Post Reply