Canvas properties: Difference between revisions

Jump to navigation Jump to search

Canvas properties (view source)

Revision as of 16:40, 4 July 2012

3,680 bytes removed ,  4 July 2012
m
→‎Todo: fgCanvas (standalone canvas rendering analogous to fgpanel): moved to FGCanvas
Line 48: Line 48:
* Support implementing GUI widgets using Canvas/Nasa (currently being discussed)
* Support implementing GUI widgets using Canvas/Nasa (currently being discussed)
* Static image files should be handled like any other element on the canvas. Only instead of specifying a path you'll have to set the file system path to an image which will be loaded with osg.
* Static image files should be handled like any other element on the canvas. Only instead of specifying a path you'll have to set the file system path to an image which will be loaded with osg.
=== Todo: fgCanvas  (standalone canvas rendering analogous to fgpanel) ===
Objective: Brainstorming of all ideas related to fgpanel-related functionality for the new Canvas subsystem
* '''Torsten''': "fgpanel is the 2d-panel code from flightgear wrapped into a simple standalone application being able to display 2d instruments on very simple hardware with basic OpenGL support. Find the sources dropped here: http://www.gitorious.org/flightgear-pmpt/panel " [http://flightgear.org/forums/viewtopic.php?f=6&t=9966&p=135101&hilit=fgpanel#p101041]
* '''James''': " I am going to be overhauls the 2D panels / displays code in the near future, and was planning to create exactly the same idea - a standalone app that can run a single panel - good to know the idea works! (I'm also planning to internally port the 2D panel code to the new system, but that should be invisible to most people)" [http://flightgear.org/forums/viewtopic.php?f=6&t=9966&p=135101&hilit=fgpanel#p101044]
* '''Hooray''': "the standalone 2D panel is actually a great idea, and if this could be improved on, this could make other solutions (like openGC) obsolete. I think that's important because there are so many similar projects. maybe there is a way to use FG itself in a special "mode" for just rendering 2D instruments, getting the properties for each instrument from a master fgfs instance.Such a new "instrument only"-mode could then run with most subsystems disabled (like i.e. sound, fdm, weather, scenery, terrain etc) and only render FG XML instruments. The corresponding properties could then be retrieved from the fgfs main instance, probably using a custom protocol. So I really like the idea of having a standalone mode, but I am not sure if it should be a completely separate code base (sounds like maintenance hell to me actually). Instead, it would probably make sense to make some more subsystems optional so that they can be disabled on demand, then the same fgfs binary could be used for starting up in an "instrument only" mode that only renders 2D instruments with properties being read from a master instance." [http://flightgear.org/forums/viewtopic.php?f=6&t=9966&p=135101&hilit=fgpanel#p101046]
* '''James''': "That's more or less exactly what it will be - and yes, it will be part of the main FG codebase, not a fork. As you say, the hope is to make fggc and some related things obsolete, since the same XML+Nasal can be used in the main sim or stand-alone. " [http://flightgear.org/forums/viewtopic.php?f=6&t=9966&p=135101&hilit=fgpanel#p101056]
* '''Hooray''': "At some point looking again into [http://cigi.sourceforge.net/ cigi] might actually be interesting to handle fgfs<->fgpanel communications, as you may remember, cigi was first brought up some time ago in the DIS/HLA thread and would seem like a perfect match in this context, it's all open source (GPL in fact) and an established standard used by many major players in the aviation industry:" [http://flightgear.org/forums/viewtopic.php?f=6&t=9966&p=135101&hilit=fgpanel#p134964]
* '''James''': "Creating a 'fgcanvas' client analogous to 'fgpanel' should be doable too, since the canvas simply renders to a single osg-Camera. Unlike fgpanel this will require OSG instead of raw GL of course, but that's the price we pay for unifying the rendering backend." [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg37441.html]
* '''Hooray''': "Regarding Torsten's fgpanel work, it would be good to eventually generalize this in such a fashion, that "canvas" instruments could also be rendered standalone at some point."
Some more ideas have been collected here: [[SGModule - standalone SGSubsystems]].


=== Vector Images ===
=== Vector Images ===
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/51542"

Navigation menu