> > • To support facetizing multiple-primitive, i.e. the combination,
I am trying to write a new version of import5 and export5 according to the
similar parts in comb.c and nmg.c. Because it should traversal not only the
BRL-combination tree, but also the shell structure.
>
> Can you explain the intention here in more detail? Modifying
import/export implies the database format might be changing. That would
introduce a major format incompatibility and we are very cautious and
intentional about doing that.
This is exactly the intention of the rewrite: Keeping the binary format the
same despite the changed nature of the nmg primitive. I.e. handle an old
multiple-shell primitive with the help of combinations so that it shows the
same behavior during ray-trace as before.
And the new nmg will be memorized with a single model, nmgregion and shell
with it. This way older versions can still read it.
Regards,
Daniel
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
