On Sat, Jun 6, 2015 at 6:50 PM, Christopher Sean Morrison <brl...@mac.com> wrote: > > On Jun 6, 2015, at 11:55 AM, Clifford Yapp <cliffy...@gmail.com> wrote: > > 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 > > > Notice how the above statement is inconsistent with...
Sorry, imprecise language on my part. By "that" I was referring strictly to the graphical part (i.e. the part of the task where libdm is involved.) > The key bit from BRL-CAD as far as I can see > is [snip] librt and the step-g importer logic (which is > ideally libgcv)? > > That is why I said BRL-CAD is requisite (I did not say libdm). At least > until libgcv is a separate API download, there is no additional complexity > to use libdm. From a dependency standpoint, true. > - in particular, > since Qt is already being proposed for the GUI part of the viewer, > > It is not being proposed... > > The project plan (which I highly recommend reading, Milinda was > exceptionally thorough! excellent detail) originally called for OC but it > was replaced with libdm after some discussion. It's worth trying only > because it would keep dependencies to a minimum. I was looking specifically at section 3.4 on melange (2.5 in the dropbox pdf) which discusses the GUI and lists Qt... is there a more current version I should check? (Apologies if I missed it...) > I wouldn’t even suggest requiring librt or BRL-CAD at all, but I don’t > believe manually extracting wireframes or polygons is doable in the GSoC > timeframe (especially now that we’re two weeks in). Keeping things simple, > I would suggest just fixing the current issue (which is a simple > preprocessor issue) or jumping to the next-least-complex dependency (GLUT). > For this type of simple stand-alone application, GLUT is a viable option, > but I’d still give libdm a few more days before throwing in the towel. If Qt isn't part of the mix already I guess I agree. > 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 > > I agree other than “it was not going to be used.” Apologies if I misinterpreted the plan or looked at an old version. CY ------------------------------------------------------------------------------ _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
