I thought of that (  mco:foo( mco:bar(event),event)  ) but thought that our 
declarative argument parser was hairy enough as it was; admittedly you could 
just recurse in when you find an mco, but I think (what is essentially) piped 
output is clearer and makes the evaluation order first-last, as it would have 
been if my initial, multiple-"onXXX=aHandler" proposal were permissible.

(Of course, keep in mind that I'm not fond of the mco syntax; I still want an 
xml syntax with named parameters...this is distinct from any illusion we'll get 
it.)


-----Original Message-----
From: Trevor Oldak (JIRA) [mailto:[EMAIL PROTECTED]
Sent: Wed 3/7/2007 3:39 PM
To: [email protected]
Subject: [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_12478885
 ] 

Trevor Oldak commented on XAP-317:
----------------------------------

Suppose we could say:

mco:A.bar(mco:A.foo(event), event)

thus making a mco a valid argument for another mco call. That was we use the 
mco's already exist unique identifier (its ID) and elminate any issues from 
people who want an element with id LAST_RESULT.




> 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.


Reply via email to