4,400
edits
Canvas properties: Difference between revisions
Jump to navigation
Jump to search
m
Update forum links
m (→Element/Group Defaults: remove old/outdated talks) |
m (Update forum links) |
||
| Line 50: | Line 50: | ||
* '''Hooray''': "yes, sounds like the best and most powerful design to me, because everything would still be a canvas, but nesting/recursion would be supported, i.e. "piping" the output from one canvas into another canvas group, so that canvases can be reused and nested" {{Done}} | * '''Hooray''': "yes, sounds like the best and most powerful design to me, because everything would still be a canvas, but nesting/recursion would be supported, i.e. "piping" the output from one canvas into another canvas group, so that canvases can be reused and nested" {{Done}} | ||
* '''TheTom''': "Maybe I should add means to define clipping regions to guarantee widgets can't draw outside their assigned regions, i.e. perform clipping only if there is actually a clipping region specified." {{Not done}} | * '''TheTom''': "Maybe I should add means to define clipping regions to guarantee widgets can't draw outside their assigned regions, i.e. perform clipping only if there is actually a clipping region specified." {{Not done}} | ||
* '''Omega95''': "Supporting 3D objects to be projected onto canvas" [http://flightgear.org | * '''Omega95''': "Supporting 3D objects to be projected onto canvas" [http://forum.flightgear.org/viewtopic.php?f=71&t=17278#p164260] | ||
| Line 121: | Line 121: | ||
<references/> | <references/> | ||
See [[FGPlot#Feature_Requests]]: provide a new Nasal API to serialize a canvas texture (or group) to an osg::Image in $FG_HOME, so that graphs can be easily saved and shared/posted without users having to take full screen shots and then having to edit the image [http://flightgear.org | See [[FGPlot#Feature_Requests]]: provide a new Nasal API to serialize a canvas texture (or group) to an osg::Image in $FG_HOME, so that graphs can be easily saved and shared/posted without users having to take full screen shots and then having to edit the image [http://forum.flightgear.org/viewtopic.php?f=49&t=17540&hilit=gnuplot#p166472] | ||
providing a hook to get a binary dump of the a canvas texture (i.e. as a PNG file) | providing a hook to get a binary dump of the a canvas texture (i.e. as a PNG file) | ||
| Line 136: | Line 136: | ||
=== Render 3D models to a texture === | === Render 3D models to a texture === | ||
Omega95 mentioned how being able to load a 3D model and transform/render it to a 2D texture would allow more complex instruments and GUI widgets to be implemented using the Canvas system. This should probably be added as a custom canvas "mode", and it should probably be implemented such that it may later on be extended to also support scenery views using CompositeViewer or FlightGear aircraft [http://flightgear.org | Omega95 mentioned how being able to load a 3D model and transform/render it to a 2D texture would allow more complex instruments and GUI widgets to be implemented using the Canvas system. This should probably be added as a custom canvas "mode", and it should probably be implemented such that it may later on be extended to also support scenery views using CompositeViewer or FlightGear aircraft [http://forum.flightgear.org/viewtopic.php?f=4&p=164245#p164243]. {{Not done}} | ||
=== Smart Labels for OSGText elements === | === Smart Labels for OSGText elements === | ||
| Line 148: | Line 148: | ||
::: Note that [http://pal.heig-vd.ch/index.php?page=about-pal PAL] requires [http://trac.osgeo.org/geos/ GEOS], both use an autotools based build system. | ::: Note that [http://pal.heig-vd.ch/index.php?page=about-pal PAL] requires [http://trac.osgeo.org/geos/ GEOS], both use an autotools based build system. | ||
Also see: http://flightgear.org | Also see: http://forum.flightgear.org/viewtopic.php?f=71&p=166909#p166909 | ||
=== Vector Data Cache === | === Vector Data Cache === | ||
| Line 168: | Line 168: | ||
Also, see: | Also, see: | ||
* http://flightgear.org | * http://forum.flightgear.org/viewtopic.php?f=71&t=21090 | ||
=== Integration with the Effects/Shader framework {{Not done}} === | === Integration with the Effects/Shader framework {{Not done}} === | ||