On Jun 1, 2011, at 12:58 PM, Christopher Sean Morrison wrote:
> May have just found the answer to my own question.. was the geometry engine
> left in rt^3? I see unit test dirs and some sources in oldstuff, but no core
> code.
Indeed that seems to be the case, got a full build of the GS after
compiling/installing the GE sources from rt^3. That'll be a little tricky to
resolve for Ohloh accounting purposes since geomcore was branched then purged.
It's all cool, though... we just may have to move geomcore and rt^3 sources
around once again (into new modules) so there is unique history for both.
The proper separation of the main BRL-CAD libs, the Geometry Engine API, and
the Geometry Service application(s) is a good one. It reinforces the layered
design and makes it a lot harder to introduce cyclic dependencies. So the
question becomes what to name the new modules. Any suggestions?
Geometry Engine candidate names:
/svnroot/brlcad/ge/trunk
/svnroot/brlcad/GE/trunk
/svnroot/brlcad/geometryengine/trunk
/svnroot/brlcad/GeometryEngine/trunk
Geometry Service candidate names:
/svnroot/brlcad/gs/trunk
/svnroot/brlcad/GS/trunk
/svnroot/brlcad/geometryservice/trunk
/svnroot/brlcad/GeometryService/trunk
Other ideas? Absent commentary, I'll just flip a coin and start restructuring
this weekend. (leaning towards ge/gs or GE/GS)
Cheers!
Sean
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
