The trim-nurbs branch has since been merged in with the trunk, but the librt dir is where most of the action is at. More specifically:
src/librt/primitives/brep/brep.cpp src/librt/opennurbs_ext.cpp include/opennurbs_ext.h include/on_brep.h include/brep.h src/other/openNURBS/ src/proc-db/*.cpp In brep.cpp is the guts to the implementation starting with the fundamental representation and ray-tracing. It uses the openNURBS library for the basic boundary representation data structures but the library doesn't provide evaluation support so that's the bulk of what we have to implement for ray-trace support. So we basically extend the library (hence the ext files) where needed. The proc-db examples create some simple testing geometry. It's all in a big state of flux and subject to lots of changes, but that's where things presently stand. Cheers! Sean On Aug 11, 2008, at 10:41 PM, Tom Browder wrote: > On Mon, Aug 11, 2008 at 7:00 PM, Christopher Sean Morrison > <[EMAIL PROTECTED]> wrote: > ... >> Tom, >> >> The plan (so far) is indeed to use openNURBS as the representation >> structure >> for implementing spline surface BREP objects. Alas, openNURBS >> (intentionally) doesn't provide most of the necessary evaluation >> routines, >> so we're still left with a fair bit of work. >> >> The developers portions that need to happen for full BREP >> evaluation (some >> of which are already working or under development) are to implement: >> >> 1) a new BREP primitive in LIBRT with I/O support (done) >> 2) support for ray tracing BREP objects (partially done) >> 3) descriptor routines for all existing primitives to describe >> themselves as >> a BREP (partially done) >> 4) a BREP-BREP intersection evaluation routine (entails a variety of >> subroutines) >> 5) CSG evaluation of BREP objects to provide evaluated BREP results >> 6) tessellation of BREP surfaces (partially done) >> >> Once those happen, the functionality can be hooked into new/existing >> converters and should give an exceptionally more robust conversion >> route >> among other benefits. Right now, we're mostly on 2 and 3. >> >> If someone is interested in helping any of those tasks move >> forward, there >> are some references that could probably be dug up. > > Thanks for the update, Sean, this capability is very important to me, > and perhaps I can help in some modest way. > > It looks like the hot spot is the librt dir in the trim-nurbs branch. > Is there a best place to start trying to get familiar with the action? > > -Tom ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
