On Jan 9, 2017 8:38 AM, "Alex Harui" <aha...@adobe.com> wrote:
In the PAYG philosophy, there are beads that are essentially write-once (or non-dynamic), and beads that are dynamic. In many smaller applications, you set something and never change it. So why carry all of the code around for things that aren't needed. For a write-once bead, it should hold its properties until the strand is set, then apply the properties and it is done. For dynamic beads, they might need to keep a host or strand property, and have change detection and change events, and even an invalidation subsystem if needed. So, if you need all of that in MDL and Fontawesome, go ahead and add it there. Yes, this is inline with what I expected. Is there an example of a dynamic bead in one of our examples or components? Thanks, Om My 2 cents, -Alex On 1/9/17, 1:42 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote: >On Mon, Jan 9, 2017 at 1:33 AM, piotrz <piotrzarzyck...@gmail.com> wrote: > >> Ahh! Yes! :) >> >> I'm wondering whether we are assigning everywhere values in setter and >>in >> strand additionally. Need to review all beads. >> > >For what it's worth, I just tried it after your initial comment, but it is >near impossible to access the host.element in a function outside of the >set >strand() method. I'm guessing it is because we need >the @flexjsignorecoercion directive. > >Thanks, >om > > >> >> Piotr >> >> >> >> >> >> ----- >> Apache Flex PMC >> piotrzarzyck...@gmail.com >> -- >> View this message in context: http://apache-flex- >> development.2333347.n4.nabble.com/Re-git-commit-flex-asjs- >> refs-heads-feature-fontawesome-Add-Animate-bead-for-FontAwesomeIcon- >> tp58033p58038.html >> Sent from the Apache Flex Development mailing list archive at >>Nabble.com. >>
