glider workbench
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
glider workbench
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.
- DeepSOIC
- Veteran
- Posts: 7896
- Joined: Fri Aug 29, 2014 12:45 am
- Location: used to be Saint-Petersburg, Russia
Re: glider workbench
Cool!
At the moment, I'm not interested in it, but it' cool anyway. I wonder, how many purpose-specific workbenches are out there.
At the moment, I'm not interested in it, but it' cool anyway. I wonder, how many purpose-specific workbenches are out there.
Re: glider workbench
Looking good.
Re: glider workbench
that is really interesting
Re: glider workbench
VERY nice looo! The code looks very clean too, congrats
Re: glider workbench
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.
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.
- microelly2
- Veteran
- Posts: 4688
- Joined: Tue Nov 12, 2013 4:06 pm
- Contact:
Re: glider workbench
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
Can you check it for your? If you commit it into your git - the workbench is integrated.
https://github.com/microelly2/freecad-p ... 3e1ee947b7
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
Re: glider workbench
thanks for your efforts.
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.
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.import freecad_glider cannot work inside the same directory, to get the 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.
- microelly2
- Veteran
- Posts: 4688
- Joined: Tue Nov 12, 2013 4:06 pm
- Contact:
Re: glider workbench
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.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.
seems that this is the right place for discussion: viewtopic.php?f=22&t=13238
- microelly2
- Veteran
- Posts: 4688
- Joined: Tue Nov 12, 2013 4:06 pm
- Contact:
Re: glider workbench
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)
There are still some small problems - see this thread above.
after that finished I post how to get all installed (you need openglider too)