Open sumpfralle opened 5 years ago
I'm sorry to hear you want to use a web browser widget or a separate browser. I'm sure there can be a better solution. It does not seem an enhancement...
I wouldn't mind a web browser (widget) based approach, FWIW. But isn't the point also that once expressed in X3D, the choices for a rendering platform are open?
To me the web-widget is an ugly approach and a crude hack.
the choices for a rendering platform are open?
Yes. At least in Debian I see view3dscene, but it is probably not possible to control this rendering externally. Thus the javascript-based rendering via x3dom looks like my favorite option for now.
To me the web-widget is an ugly approach and a crude hack.
I would be happy, if someone would take over the maintenance of the current OpenGL legacy code in pycam and port it to the current OpenGL standards: 3.x (since 2008) or maybe even 4.x (2010). I am quite sure, that no new graphics hardware sold today is able to render the OpenGL commands in pycam (targeting 2.x, 2004) anymore. Thus a change is inevitable. Just the direction of progress is open for discussion. I welcome any input.
Just for the curious:
Up to now the migration from OpenGL to X3D was surprisingly easy:
But there is a good amount of details left for bringing it back to the previous level of comfort:
The current state is available in the branch replace-opengl-with-x3d
- but it is surely only suitable for the daring souls ...
Due the broken state of the current OpenGL visualization (see #134), it would be good to find another method for visualizing the current model and toolpaths.
Maybe X3D would be a good candidate.
It could work like this:
This will also be useful in case anyone wants to implement a web-based application around pycam's scripting feature.