2014-03-05 1:26 GMT+01:00 Christopher Sean Morrison :
>
> On Mar 2, 2014, at 2:09 PM, Daniel Roßberg wrote:
>
>> The C++ interface isn't part of the main "brlcad" branch yet. I
>> couldn't find the right place there. One reason is that I pursue a
>> little different direction of system integratio
On Mar 2, 2014, at 2:09 PM, Daniel Roßberg wrote:
> The C++ interface isn't part of the main "brlcad" branch yet. I
> couldn't find the right place there. One reason is that I pursue a
> little different direction of system integration. In case of
> Unix-like operating systems I like to follow
The C++ interface isn't part of the main "brlcad" branch yet. I
couldn't find the right place there. One reason is that I pursue a
little different direction of system integration. In case of
Unix-like operating systems I like to follow the Filesystem Hierarchy
Standard, i.e. all headers in /usr
On Sun, Mar 2, 2014 at 3:15 AM, Daniel Roßberg
wrote:
> Tom,
>
> It looks like you hadn't a look at the BRL-CAD core C++ interface in rt^3.
Sorry, Daniel, you're correct. I haven't looked at it in a long time.
I apologize.
> BTW, do you know the BRL-CAD viewer for Windows?
No, I don't
> It w
Tom,
It looks like you hadn't a look at the BRL-CAD core C++ interface in rt^3.
It's true that it isn't ready yet. But it is relatively small, simple and
close to the C functionality. It has all you need to load a database (in 3
modes), traverse the tree, raytrace, work with attributes and make
I wonder if this might be a suitable GSoC project:
+ provide a simple, C++ interface to a limited set of BRL-CAD
functions for ray tracing, e.g., as typically used in vulnerability
analysis
I know we have rt^3, but that's a giant project in itself, although I
guess work on that would be more effi
