Currently there are two ongoing efforts to create a C++ wrapper for BRL-CAD.

First, there is my project (supported on code contributions from TNO)
to write the C++ layer right on top of the core functions (mainly
provided by librt).  This way I want to
- create an easy to use interface which
- is not effected by changes to the inner (librt etc.) structures,
- is fast and
- acts as a reference on how to use BRL-CAD's core functions.

This interface shall be used in other fast running programs.  One
problem which arises then is the decision about the owners and live
times of the objects.  I don't want to use memory allocation or string
comparisons in simple operations.  A solution is the use of call backs
(which may look ugly for some people).  Well, we will see how far I
will go with this.

The other C++ interface project is part of iBME (Integrated BRL-CAD
Modeling Environment) with David Loman as the main developer of its OO
design.  It will use BRL-CAD via libged's command-line like interface.
 There I would like to know more about the reasons for the design.
What are the intended applications?

In my opinion these two projects are trying to develop different
layers on BRL-CAD (iBME a more abstract, higher layer than mine).
Maybe iBME's Geometry Engine could be based on my core interface.


Sziasztok,
        Daniel



PS: Both projects have a wiki-page on brlcad.org and their source code
can be found on brlcad.svn.sourceforge.net/brlcad/rt^3 at
include/brlcad, src/coreInterface or src/iBME respective.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Reply via email to