20,741
edits
Canvas news: Difference between revisions
Jump to navigation
Jump to search
m
→2D Panels: https://forum.flightgear.org/viewtopic.php?f=14&t=33454&p=324618#p324618
(→2017) |
m (→2D Panels: https://forum.flightgear.org/viewtopic.php?f=14&t=33454&p=324618#p324618) |
||
| Line 634: | Line 634: | ||
=== 2D Panels === | === 2D Panels === | ||
James has done most of the work to port the 2D panels to use Canvas, and will do the C++ HUD next, and hence is creating Canvas elements bypassing the Nasal API.<ref>{{cite web | |||
James is working towards migrating 2D panels to use the Canvas<ref>https://sourceforge.net/p/flightgear/mailman/message/35623408/</ref>. | |||
This step was inspired by a discussion that originally took place on the devel list, i.e. we should move the 2D panel and HUD rendering over to this approach, since that would get rid of all the legacy OpenGL code besides the GUI. <ref>https://sourceforge.net/p/flightgear/mailman/message/29584988/</ref> | |||
Moving the HUD to use the Canvas would be a great step from his point of view, since it and 2D panels (which he is happy to write the convert for!) are the last places besides the UI which make raw OpenGL calls, and hence would benefit from moving to the Canvas (and thus, to use OSG internally) <ref>https://sourceforge.net/p/flightgear/mailman/message/30058187/</ref> | |||
The original goal was to identify common requirements to seee how we manage XML / property-list file processing in a nice way, to support the various formats we want to create canvas elements from - GUI dialogs, 2D panels and HUDs.<ref>https://sourceforge.net/p/flightgear/mailman/message/29588419/</ref> | |||
James is planning in the next couple of weeks to port the panel code to generate Canvas elements, and then submit my fgcanvas utility to render any Canvas remotely, That code currently users software rendering (too slow for the RaspberryPi he expects), but upgrading the code to use OpenGL ES2 rendering is next on his todo-list so he can fun on Android / iOS devices as well as Raspbery Pi. If you’re interested in working on that please let him know, he would be glad of the help.<ref>https://sourceforge.net/p/flightgear/mailman/message/35552824/</ref> | |||
James has done most of the work to port the 2D panels to use Canvas in an experimental branch<ref>https://sourceforge.net/p/flightgear/mailman/message/35691472/</ref>, and will do the C++ HUD next, and hence is creating Canvas elements bypassing the Nasal API.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35574596/ | |url = https://sourceforge.net/p/flightgear/mailman/message/35574596/ | ||
|title = <nowiki> Re: [Flightgear-devel] Observation about the Canvas Z-ordering </nowiki> | |title = <nowiki> Re: [Flightgear-devel] Observation about the Canvas Z-ordering </nowiki> | ||