>>For what it’s worth, ensuring robust and faithful 3DM import and export
support in LIBGCV would be immensely valuable, and probably be the next
best step. We do not >>have a 3DM exporter, but writing one is pretty
trivial (probably take less than a week for non-CSG geometries).
trying to get familiar with the .3dm file format, cannot seem to find much
information on the web. src/other/openNURBS is already been build during
make, but the important file that I was looking for (example_read/
example_write/ ) is no longer in the SVN. I downloaded opennurbs_20130711
But have problem compiling (Sean seems to have the same problem 6 years
ago). Instead of making opennurbs_20130711 compile cleanly with example
executable generated, I think I will try to link to the opennurb library
inside brlcad with the example read/write code. Unless brlcad have a way to
regenerate those (example_read/ example_write/ ) inside opennurb easily?
opennurbs_20130711 > ls | grep /
build_opennurbs_xcode.xcworkspace/
example_brep/
example_gl/
example_read/
example_roundtrip/
example_userdata/
example_write/
opennurbs.xcodeproj/
zlib/
On Wed, Mar 9, 2016 at 6:06 PM, Christopher Sean Morrison <brl...@mac.com>
wrote:
>
> Please keep communications public. No need to be shy. This is how we all
> learn.
>
> For what it’s worth, ensuring robust and faithful 3DM import and export
> support in LIBGCV would be immensely valuable, and probably be the next
> best step. We do not have a 3DM exporter, but writing one is pretty
> trivial (probably take less than a week for non-CSG geometries).
>
>
>
> On Mar 9, 2016, at 8:57 PM, Margaret Hu <margaret.ss...@gmail.com> wrote:
>
> >>This characterization does not sound right. Make sure you're looking at
> an SVN checkout and not a source tarball, and interpreting what you see
> there correctly. Also >>make sure you're looking in the source dir and not
> the build dir.
> Yes I was looking at the build dir, which is not complete. I see the src
> dir has most of the obj, stl, vrml there. Now the step seems rather
> complicated with various spec like 214, 242, 203. The iges also looks
> complicated, I will see if I can pick one for the gsoc proposal, dxf seems
> to be a good test of concept, not too complicated.
>
>
>
>
> On Wed, Mar 9, 2016 at 4:52 PM, Christopher Sean Morrison <brl...@mac.com>
> wrote:
>
>>
>> Some work has already started at the obj part, the lex/yacc grammer/token
>> is already there while stl and vrml exists only as a skeleton directory.
>>
>>
>> This characterization does not sound right. Make sure you're looking at
>> an SVN checkout and not a source tarball, and interpreting what you see
>> there correctly. Also make sure you're looking in the source dir and not
>> the build dir.
>>
>>
>> Is there a SVN checkout of the test cases for the src/conv directory,
>> where can I find some small yet representative 3D files of various format?
>>
>>
>> Nope.
>>
>> Cheers!
>> Sean
>>
>>
>>
>
>
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
