Hello Sean,
On 20 March 2015 at 05:02, Christopher Sean Morrison <brl...@mac.com> wrote:
>
> Really the only valid reason for implementing a library that is already
> readily available would be because they are license incompatible or yours
> will be substantially and non-subjectively better in some way. That
> usually means faster or less memory or new features. Just because
> something provides features X, Y, and Z when you only need feature X is not
> a strong position.
>
>
Your response has given me some light on what path to follow. I
have been revisiting some options and I think white dune
<http://vrml.cip.ica.uni-stuttgart.de/dune/> would be great for X3D
parsing. It has great support for vrml and x3d including support for nurbs.
Some of the files I used to test the vrml-g converter were X3D
NurbsPatchSurface and NurbsPatchSolid files which I converted to vrml
polygonal representation using white dune and so I really appreciate its
functionality. The source code is about 44MB out of the box and it uses
GNU GENERAL PUBLIC LICENSE Version 2. I have been able able to reduce the
code to about 12MB but it still takes a noticable amount of time to compile
I think I can be able to reduce it to less than 7MB by isolating the code
essential for parsing but that would take some time and better
understanding of the code and also I have not encountered any issues with
dependencies.
Thanks
Konrad
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel