What new or enhanced feature are you proposing?
Currently, EventTriggers are single model elements that have no references to
other data sources.
This should be changed; when an event is fired, it should be able to contain
references to additional data, that are populated when the event is fired. This
is argued for on the C2 wiki. For example:
- The containing element that fired the event
- The reason the event was fired (e.g. onSelect: selected by a keyboard, or the
mouse)
- For onClick, the (x,y) of where the user clicked
- For Email onFailure, the cause of the e-mail send failure
For keyboard modelling, this may be a fundamental requirement (e.g. onKeyPress
needs access to the key pressed).
These references could be contained directly as children within the event
itself.
What goal would this enhancement help you achieve?
More expressive web applications.
Original issue reported on code.google.com by soundasleep on 9 Jun 2010 at 12:56
Original issue reported on code.google.com by
soundasleep
on 9 Jun 2010 at 12:56