On Apr 03, 2012, at 11:58 AM, phoenix <284281...@qq.com> wrote:
> The -t option would denote you want to output a tree, and root_brep would contain a reproduction of the tree structure of root using names for objects with_suffix appended, defaulting to _brep if no root_suffix string is supplied. This would leave the original tree intact, which you will want to use for comparisons. The "brep root" form of the command suggests to me generating a single brep representing the entire evaluated CSG tree, which requires NURBS surface/surface intersection - a major project all by itself. We will eventually want to do that, so we want to leave the logic syntax for it open, but it's for later - for this project we want to just duplicate the CSG tree structure while pointing to the brep representations of the individual implicit primitives.The new syntax is a good idea, expressing clearly what it's going to do. Thanks for your suggestion.NURBS intersection, once implemented, can be applied immediately after this conversion, when a tree with brep representations is built.
Your proposal only needs to account for your time and what products or features will result. That means allocating time towards the creation of a tool/command, identifying it as a milestone, and including time for interface design and discussions.
Cheers!
Sean
------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
