t;
>> We have still two months evaluation work before making our decision...
>>
>> Nicolas Granon
>>
>>
>>
>>
>>> -Message d'origine-
>>> De : Yishay Weiss [mailto:yishayj...@hotmail.com
>>><mailto:yishayj...@hotmail.com>]
&g
will benefit.
Thanks,
Yishay
From: Idylog - Nicolas Granon<mailto:ngra...@idylog.com>
Sent: Thursday, November 2, 2017 12:59 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: Event Metadata
Thank you for your answer.
You say that there is no sure way to know which is fa
h
>already contains some beads.
>In that case, the "inner" component (the base class) is considered as a
>strand and the global logic is the same as in case (2).
>
>All in all, this is not very different from what happens in classic Flex
>when building "complex " compon
ich are really composited, not
simple subclasses).
Too naïve to be useful, maybe ???
Nicolas Granon
> -Message d'origine-
> De : Peter Ent [mailto:p...@adobe.com.INVALID]
> Envoyé : mardi 31 octobre 2017 20:39
> À : dev@royale.apache.org
> Objet : Re: Event Metada
I typically use the strand as the central dispatcher for intra-bead
communication. Sometimes an event from a bead conflicts with an event
dispatched by the strand to the "outside". For example, if a bead were to
need to send a "change" event and another bead was listening for that
event, "change"
For 1) the rule already is that if you want to access an implicit bead you
have to explicitly declare it. So if a bead is normally brought in via
CSS, you instead declare that bead on the strand and make adjustments.
UIBase doesn't care how the beads get placed on the strand, and all bead
loading
