Hi Himar,
The simplicist thing would be to work with the community to allow you
to use GraphicsWindowWin32 without mods at your end, this may mods to
GraphicsWindowWin32 itself to facilate your particular usage. I could
also be that you don't even need to modify GraphicsWindowWin32 at all,
and just set it up differently.
I know nothing of WPF though, nor Win32 API so this is topic to
discuss amongst other Windows users - i.e. would do we get it
supported easily.
I don't know if it has any bearing by the C# wrappers are using
osgViewer just fine.
Another thing to bare in mind is that you can explictly use your own
GraphicsWindow's by just pass them to the osg::Camera. See examples
like osgcamera.
Robert.
On 6/26/07, Himar Carmona <[EMAIL PROTECTED]> wrote:
That's why i did a comment about it. There is no problem to publish the
modifications under OSGPL. If i understood the license
terms correctly (i'm a programmer, not a lawyer and never woriking with
LGPL before), if i modify some parts of OSG, i must publish them under
OSGPL, right? But because OSGPL is based on LGPL, i can use OSG in any
commercial product with his own license terms. That's right? I'm using OSG
to develop a commercial product.
Now, ending the legal part of my comment, three more questions:
1) i don't know if the changes i did may be of interest to be merged
with the OSG streamline. May i comment what i did and someone else value it?
2) It is possible to Subclass GraphicsWindowWin32 and let OSG create a
new instance for the subclass? How? I didn't found how. If it is possible, I
prefer to do it this manner, because now i have my own implementation of
GraphicsWindowWin32 and i don't like it (i can't update with the latest
developments). I let
osg::GraphicsContext::createGraphicsContext create the
instance for me and Win32WindowingSystem seems to be statically registered
and coupled to GraphicsWindowWin32.
3) May i relate my tests? Perhaps it could be helpful for someone else.
(OSG integration with WPF using Win32, pre osgDotNet). I have been asking a
lot since i started with OSG. Of course, they are platform specific...
Haven't read before the osgbooks site. Great news!!
Thanks a lot.
Himar.
2007/6/26, Robert Osfield <[EMAIL PROTECTED]>:
>
> On 6/26/07, Himar Carmona <[EMAIL PROTECTED]> wrote:
> > Thanks, Mr. Osfield,
> >
> > your patience is grateful.
> >
> > I'm using exactly Win32 directly and WPF as frontend. Thanks to your
> > advises, i have achieved a WPF application with an OSG window inside
(needed
> > to modify GraphicsWindowWin32 a bit due to WPF requirement). Now i have
a
> > base code to start my GIS development. I will look carefully at the
examples
> > you mentioned, it's great to have such a bunch of them!
>
> Please note the the OSGPL license requires you to publish
> modifications of the OSG source code under the OSGPL.
>
> Subclassing from OSG classes doesn't not constitute modifications of
> the OSG source code so it is perfectly legal license this how you
> wish.
>
>
> > There is a Quick Start Guide, a Reference Manual, is there any plan to
> > develop an 'Complete OSG Guide' or 'OSG Tips and tricks' or whatever any
> > more documentation? The QSG is a great job, but for a new user like me,
it
> > is so great explained, that i miss the 2nd part. In my opinion it
doesn't
> > reflect the whole potential that OSG have (and the wonderful work it
is).
> > There are a lot of code, explanations and tips spreaded out. :(
>
> See the osgbooks website.
> _______________________________________________
> osg-users mailing list
> osg-users@openscenegraph.net
> http://openscenegraph.net/mailman/listinfo/osg-users
> http://www.openscenegraph.org/
>
_______________________________________________
osg-users mailing list
osg-users@openscenegraph.net
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
_______________________________________________
osg-users mailing list
osg-users@openscenegraph.net
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
