You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xap-dev@incubator.apache.org by "Turyn, Michael (JIRA)" <xa...@incubator.apache.org> on 2007/03/07 19:26:24 UTC
[jira] Commented: (XAP-317) It would be good to have stackable
events for our elements.
[ https://issues.apache.org/jira/browse/XAP-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478859 ]
Turyn, Michael commented on XAP-317:
------------------------------------
...plus it would be a good idea not to violate the rules for well-formed XML.
Additional thought: if we've got multiple mcos, it would be useful to have a reserved word for the return value of the last operation:
"mco:foo();mco:bar(LAST_RESULT,event);"
Downside: it approaches the danger of trying to create another scripting language.
> It would be good to have stackable events for our elements.
> -----------------------------------------------------------
>
> Key: XAP-317
> URL: https://issues.apache.org/jira/browse/XAP-317
> Project: XAP
> Issue Type: Improvement
> Components: Macros, MCOs, Widgets, XML Dom / Parsing
> Reporter: Turyn, Michael
>
> I think >1 "onXXX" event attributes on an element should be allowed;:
> <aWidgetTag onMouseDown="mco:A.foo()" onMouseDown="mco:A.bar(...)" ..../>
> ---on the mouse down event they would be called in the order declared; this would be good for cutting-and-pasting functionality modularised as MCOs and Macros.
> This is one of the best things about the Dojo connect() mechanism, and also seems to be in place for Yahoo UI dragging events.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.