That's correct. For example, the TextInput component does not have the capability to mask input for passwords. But there is a bead you can add to it (org.apache.flex.html.accessories.PasswordInputBead) that listens for changes to the text and replaces it with "*". This way only one TextInput control has the extra code.
Peter Ent Adobe Systems/Apache Flex Project On 3/15/16, 6:47 AM, "OK" <[email protected]> wrote: >>In FlexJS, PAYG will commonly be implemented with different beads > >Only to make sure if I got it right: >Does this concept mean that instead of having one fat component that >implements all the features that probably makes sense for this component >there're a couple of small beads that respectively implements only a >subset >of features according the special characteristic of this bead? >So that during application development we have to choose the bead that >best >fits our needs? > >Thanks for help, >Olaf > > > > > > >-- >View this message in context: >http://apache-flex-users.2333346.n4.nabble.com/Updating-className-tp12217p >12237.html >Sent from the Apache Flex Users mailing list archive at Nabble.com.
