Not sure I have an opinion about how the beads should work together. I'm just saying that it can be more convenient to have the beads on the same strand instead of beads with beads.
I don't think we have standards on the way the beads work together. You will probably find it is easier to require that beads be added in a certain order than having to watch the strand for new beads and search the strand for a bead, but it is easier for the consumer to use if bead order doesn't matter as much. If you consider re-use of beads, then making sure the beads don't make too many assumptions is better. IMO, instead of a MaterialIconBead with parameters, I would probably have a MaterialIconCancelBead and MaterialIconFaceBead, etc. Again, the compiler will make sure you typed it correctly, and then such a bead could probably be used in more places as it won't have assumptions about what content it will change. My 2 cents, -Alex On 11/29/16, 12:21 PM, "piotrz" <piotrzarzyck...@gmail.com> wrote: >Ok I read your post couple of times and look into the code of some Views. >Do >you mean that maybe MaterialIcons should be the beads which will be >searched >by views ? > ><mdl:Chip> > <mdl:beads> > <mdl:DeletableChip> > <mdl:MaterialIcons /> > </mdl:beads> > <mdl:view> > > </mdl:view> ></mdl:Chip> > >Piotr > > > > >----- >Apache Flex PMC >piotrzarzyck...@gmail.com >-- >View this message in context: >http://apache-flex-development.2333347.n4.nabble.com/FlexJS-MDL-Add-icon-t >o-DeletableChip-tp56766p56797.html >Sent from the Apache Flex Development mailing list archive at Nabble.com.
