You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by LiborGMC <l....@gmc.net> on 2010/03/17 16:45:47 UTC
Order of processing of mixins
Hi there,
I've implemented two mixins which just add some JavaScript code to action
onClick to actionLink. I defined these two mixins to one actionLink. I
expect that order in which mixins are fired is the same as I defined in
"t:mixins" attribute. Firefox 3 is keeping this order but IE 8 isn't. Can I
specify somehow the order of processing of mixins?
I think it is bug I would expected that behaviour is independent from type
of browser.
Regards
--
View this message in context: http://old.nabble.com/Order-of-processing-of-mixins-tp27933566p27933566.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Order of processing of mixins
Posted by Kalle Korhonen <ka...@gmail.com>.
Just in general, explicit order of listeners would destroy (current or
future) possibilities for implicit parallelism. Problems with listener
ordering can be solved with event propagation (by creating a nested
element).
Kalle
On Thu, Mar 18, 2010 at 12:27 AM, LiborGMC <l....@gmc.net> wrote:
>
> Hi, thanks for responses. I'm using 5.1.0.5. Version 5.2 brings me more pain
> than gain ;-).
> I think my problem could be somewhere else: both my mixins wired event
> handlers to same event "onclick". I don't know JS very well but could be
> possible that JS don't keep ordering when notify listeners for particular
> event. I think in Java (Swing) is the same situation.
> So mixins are processed in correct order but listeners are not probably
> notified in the same order in JS. Would you agree?
> --
> View this message in context: http://old.nabble.com/Order-of-processing-of-mixins-tp27933566p27942359.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Order of processing of mixins
Posted by LiborGMC <l....@gmc.net>.
Hi, thanks for responses. I'm using 5.1.0.5. Version 5.2 brings me more pain
than gain ;-).
I think my problem could be somewhere else: both my mixins wired event
handlers to same event "onclick". I don't know JS very well but could be
possible that JS don't keep ordering when notify listeners for particular
event. I think in Java (Swing) is the same situation.
So mixins are processed in correct order but listeners are not probably
notified in the same order in JS. Would you agree?
--
View this message in context: http://old.nabble.com/Order-of-processing-of-mixins-tp27933566p27942359.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Order of processing of mixins
Posted by Robert Zeigler <ro...@scazdl.org>.
Depends on what version of Tapestry you are using.
Explicit ordering of mixins is in trunk.
Robert
On Mar 17, 2010, at 3/178:50 AM , Michael Prescott wrote:
> As I understand it, mixin order is unspecified. A developer on our
> team had
> this issue and wound up implementing a custom component, IIRC.
>
> Michael
>
> On Wed, Mar 17, 2010 at 11:45 AM, LiborGMC <l....@gmc.net> wrote:
>
>>
>> Hi there,
>> I've implemented two mixins which just add some JavaScript code to
>> action
>> onClick to actionLink. I defined these two mixins to one
>> actionLink. I
>> expect that order in which mixins are fired is the same as I
>> defined in
>> "t:mixins" attribute. Firefox 3 is keeping this order but IE 8
>> isn't. Can I
>> specify somehow the order of processing of mixins?
>>
>> I think it is bug I would expected that behaviour is independent
>> from type
>> of browser.
>>
>> Regards
>> --
>> View this message in context:
>> http://old.nabble.com/Order-of-processing-of-mixins-tp27933566p27933566.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Order of processing of mixins
Posted by Michael Prescott <mi...@gmail.com>.
As I understand it, mixin order is unspecified. A developer on our team had
this issue and wound up implementing a custom component, IIRC.
Michael
On Wed, Mar 17, 2010 at 11:45 AM, LiborGMC <l....@gmc.net> wrote:
>
> Hi there,
> I've implemented two mixins which just add some JavaScript code to action
> onClick to actionLink. I defined these two mixins to one actionLink. I
> expect that order in which mixins are fired is the same as I defined in
> "t:mixins" attribute. Firefox 3 is keeping this order but IE 8 isn't. Can I
> specify somehow the order of processing of mixins?
>
> I think it is bug I would expected that behaviour is independent from type
> of browser.
>
> Regards
> --
> View this message in context:
> http://old.nabble.com/Order-of-processing-of-mixins-tp27933566p27933566.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>