Re: [Flightgear-devel] Switching from PUI to osgWidget

2012-07-26 Thread James Turner
On 25 Jul 2012, at 17:27, Thomas Geymayer tom...@gmail.com wrote: We could for example just add some more parseXXX functions (like parsesvg) which parse a dialog/hud/whathever file and create a canvas from it. So we would just have to modify eg. the show-dialog command to create a canvas

Re: [Flightgear-devel] Switching from PUI to osgWidget

2012-07-26 Thread James Turner
On 26 Jul 2012, at 11:09, Thomas Geymayer tom...@gmail.com wrote: I didn't meant to replace the existing way, but instead only changing the implementation to use the Canvas system in Nasal space. Just mapping the existing dialog-show command to a Nasal function which creates a window and

Re: [Flightgear-devel] Switching from PUI to osgWidget

2012-07-26 Thread James Turner
On 26 Jul 2012, at 11:28, James Turner zakal...@mac.com wrote: Maybe we can use some ideas from it :) Basically we only need to pass mouse/keyboard events and handle dragging/resizing and input focus/stacking order of multiple dialogs. This is certainly where things need to start, then.

Re: [Flightgear-devel] Switching from PUI to osgWidget

2012-07-26 Thread Thomas Geymayer
2012/7/26 James Turner zakal...@mac.com: Okay, I wasn't clear from the Wiki page what the final idea was. As you say, so long as we're going through show-dialog it should be fine. My feeling is we still want a C++ hook around creating individual widgets, so we have the option the create custom