20,741
edits
UI Unification: Difference between revisions
Jump to navigation
Jump to search
→Goals
(→Goals) |
(→Goals) |
||
| Line 29: | Line 29: | ||
Specifically, this means that UI dialogs will no longer contain any logic in the form of Nasal scripts, but that they will need to be reviewed to identify generic functionality that can be added in the form of dedicated tags for layouting, widgets, fgcommands and remote properties which can be supported by all existing, and upcoming, UI front-ends. | Specifically, this means that UI dialogs will no longer contain any logic in the form of Nasal scripts, but that they will need to be reviewed to identify generic functionality that can be added in the form of dedicated tags for layouting, widgets, fgcommands and remote properties which can be supported by all existing, and upcoming, UI front-ends. | ||
If scripting is to be supported sooner or later, it will also need to be a well-defined subset of ECMAScript that can be supported by all front-ends, e.g. by implementing a simple DSL and a corresponding parser for it (JavaScript and Nasal are close enough so that they could certainly share most of the code). | |||
== Motivation == | == Motivation == | ||