On Sat, Jun 6, 2015 at 2:11 PM, Christopher Sean Morrison <brl...@mac.com> wrote:
> That leaves options of libdm, GLUT, Qt, Wx, SDL, etc to create the window. > Given BRL-CAD is already requisite to parse and get a visual for 3D entities, > using libdm would avoid introducing a new dependency. Except I'm not sure BRL-CAD *is* requisite for that - in particular, since Qt is already being proposed for the GUI part of the viewer, it's going to be *way* simpler to have them provide a wrapped OpenGL context. That's what I meant by a "basic OpenGL window" - the OpenGL context that Qt can provide out of the box. That doesn't really introduce any new dependencies as long as Qt was going to be used anyway - OpenGL is essential for shaded 3D visuals in any case. libdm in principle can provide at least some drawing functionality without OpenGL being available, but is that a design consideration for a stand-alone STEP viewer? The key bit from BRL-CAD as far as I can see is generating the triangles from NURBS to feed to OpenGL, and that doesn't have to involve our graphics layers at all unless I'm missing something that's only librt and the step-g importer logic (which is ideally libgcv)? Given my own experiences with libdm I'm perhaps a bit gun-shy, but my first instinct is to let Qt do the hard bit of setting up the graphics context and focus on the more STEP specific bits... surely we can revisit libdm if it proves necessary/useful? Cheers, CY ------------------------------------------------------------------------------ _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
