Hi Rafa,
On Mon, Aug 10, 2009 at 7:01 AM, Rafa Gaitan wrote:
> We have been working on a solution for wrapp multiple languages from
> osgIntrospection, by now our needs run to wrapp around Java, but the
> system could be extended or refactored to allow other languages in a
> better way.
>
> Our wo
Hi Robert
>
> Longer term I'd love to see us properly solve the issues of language
> wrappers and introspection for the OSG in a way that is easy to
> maintain for all involved. What form this might take I don't know.
> My original hope was that osgIntrospection would be the basis of
> solving th
Hi,
thanks for the replies.. I'd just like to state that the aim of my request is
to get the basic swig prototypes/bindings in place, to ensure their
correctness. I think that process could be automated, somewhat.
Even though the automatically generated bindings would be unwieldy for end
use
A couple of points:
Firstly it is possible to inject C++ code in to Python quite easily using
scipy.weave. And using a cast in the C++ and the ".this" member in the Python
swig wrappers makes marshaling data between the two quite easy.
So you can write code like this:
Code:
v = mesh.ver
Hi Guys,
For 2.9.x we a not far away from a feature freeze so adding lots of
extra code is not appropriate.
Longer term I'd love to see us properly solve the issues of language
wrappers and introspection for the OSG in a way that is easy to
maintain for all involved. What form this might take I
Hi Luigi, Frank and others,
FYI I am currently using osgswig with a "patched" osg 2.9.5. This patch
consists of reverting the MixinVector stuff from osg 2.6+ with the standard
std:vector alternative in osg 2.4 so osgswig can wrap the VecArrays again. I
have tried this only on linux, and I'm not su
On Aug 4, 2009, at 7:55 AM, Luigi Calori wrote:
I'm unwilling to update as each time I update osg... there are some
problems with swig wrapping.
One of the worst issues has been the MixinVector that has broken
all the vecArrays wrapping thus preventing python construction of
geometry.
I d
Hi John and Gerwin, I' m also using osgswig... and really would like it
kept up with the osg development.
Using good python IDE such as SPE, developing osg is much easier (for
me) than in C++ . really thanks to all osgswig developers
Currently I' m stuck with an svn OSG version (2.9.5) tha
Hoi John,
I appreciate your enthusiasm for osgswig, we hear you! Including osgswig in
the main repo would certainly increase its exposure and use. However, I'm
not really sure if the "Including them would ensure that they are kept up to
date"-argument would hold just yet. There are also quite some
Hi,
the SWIG bindings are so useful, that it seems like a good idea to include them
with the main release, predicated with -DBUILD_SWIG_BINDINGS &
-DBUILD_PYTHON_SWIG_BINDINGS or -DBUILD_RUBY_SWIG_BINDINGS (etc..) flags.
Including them would ensure that they are kept up to date, and that any
b
10 matches
Mail list logo
