20,741
edits
Canvas wrappers: Difference between revisions
Jump to navigation
Jump to search
m
→HUDs: parsing 2D instruments
m (Link to special directory articles) |
m (→HUDs: parsing 2D instruments) |
||
| Line 12: | Line 12: | ||
== HUDs == | == HUDs == | ||
The HUD module will be specifically targeted at developing HUDs. | The HUD module will be specifically targeted at developing HUDs. | ||
== 2D Instruments parser == | |||
We need to write a Nasal module that will take our existing instruments in $FG_AIRCRAFT/Instruments and turn them into canvases. Namely, that means, parsing: | |||
* params | |||
* layers | |||
* transformations | |||
* conditions | |||
* actions | |||
Basically, we should already have all building blocks in place, because: | |||
* we have support for raster images: [[Canvas Image]] | |||
* event handling: [[Canvas - Event Handling]] | |||
* SGCondition bindings in Nasal (props.nas) | |||
* support for layers via Canvas groups | |||
* transformation can be directly handled through manipulation the tf properties | |||
* bindings/actions would be directly turned into Nasal callbacks | |||
In fact, the combination of Nasal and the Canvas is so much more flexible than our existing panel code, that it is foreseeable that it will see useful additions, which is why it'd be a good idea to introduce an optional version tag, so that new instruments can directly use canvas features. | |||
== GUI Widgets == | == GUI Widgets == | ||