Craig, I just took a look at the flux-2.2 code and did not see any X11 dependencies in your TriD usage. You just use the get_current_window() routine to create a drawing window. Whether the window is created with the old, raw X11+GLX method or the new *GLUT approach appears like it should not matter.
It looks like your code will be a good test to see if the new implementation works in place of the old one. --Chris Chris Marshall wrote: > Craig DeForest wrote: >> I am currently completely dependent on the X11 TriD stuff for rendering >> the output of FLUX (http://flux.boulder.swri.edu), an MHD code to >> simulate the solar corona. I have been putting off migration for three >> years and counting because various folks (including me) keep promising a >> new, cleaner TriD interface "just around the corner". >> >> I suggest a side-by-side migration strategy: a clean sweep coupled with >> deprecating the old interface. That will give me (and anyone else in my >> position) a while to migrate to the new stuff. > > That was the idea. Of course, I just downloaded the flux source > and I assume you would not being averse to the new functionality > if it supported your needs? This is exactly the type of use case > info I was hoping for. > > Thanks! > Chris > >> Cheers, >> Craig >> >> >> On Jul 11, 2009, at 7:35 AM, Chris Marshall wrote: >> >>> I would appreciate your thoughts >>> (and maybe a show of hands) about >>> maintaining the current X11 component >>> of the PDL::Graphics::TriD modules. >>> >>> Looking at the code, it appears that >>> most of the X11 and GLX stuff was put >>> in to support the creation of the >>> basic drawing window. >>> >>> The new Perl OpenGL module has moved >>> from assuming X11+GLX as the OpenGL >>> environment to one based on GLUT or >>> FreeGLUT. That immediately provides >>> cross platform portability to win32 >>> and macOS systems. >>> >>> However, while comparable functionality >>> is available to the current 3D graphics >>> within PDL, it is not compatible with >>> other X11 hacking outside PDL. >>> >>> It is tempting to make a clean sweep >>> here but it is considered bad form >>> to break existing APIs for perl modules. >>> >>> To support the old API fully, I'm >>> considering leaving in the legacy >>> PDL::Graphics::TriD code in as a >>> selectable option. That way, anyone >>> using the original code would have >>> access to it---a sort of back door, >>> if you will. If you use it now, >>> please let me know.... >>> >>> I hope/expect that the new functionality >>> and portability will make the old code >>> unused and can be removed entirely at >>> some point. >>> >>> Suggestions/thoughts? >>> Chris >>> >>> _______________________________________________ >>> Perldl mailing list >>> [email protected] >>> http://mailman.jach.hawaii.edu/mailman/listinfo/perldl >>> >> ------------------------------------------------------------------------ >> >> >> No virus found in this incoming message. >> Checked by AVG - www.avg.com >> Version: 8.5.375 / Virus Database: 270.13.10/2231 - Release Date: 07/11/09 >> 05:57:00 >> > > > _______________________________________________ > Perldl mailing list > [email protected] > http://mailman.jach.hawaii.edu/mailman/listinfo/perldl > > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.375 / Virus Database: 270.13.10/2231 - Release Date: 07/11/09 > 05:57:00 > _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
