Hi adobe-source,
We have many common widgets used in forms applications implemented
in ui-core. Writing an application of any size requires writing new
widgets to extend (or reimplement) ui-core.
In some of the work that I'm doing (general platform stuff), I don't
even know the widgets I might need, but I want to avoid sending out
any binary updates (including new widgets) if I possibly can.
What I would like is a way to define new widgets (which look correct
on the platform, support accessibility, etc) in some kind of markup,
rather than in C++. My first thoughts on this were that I needed
functions for each widget to:
- Paint, given a state.
- Return metrics.
- React to GUI events and state changes.
One idea is to expose all of the above to Lua and write new widgets
in that (and would probably end up with something similar to DOM +
JavaScript). Does anybody in ASL-land have any better ideas? I'm sure
that some of those 3 could be better described by rules than
functions..
Ralph
|
