Alex Harui wrote
> 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.
I agree that we should strive to eliminate dependencies on order. It just
makes things complicated for the user. Beads that depend on other beads can
proactively search for them and load them if necessary. Maybe we can add a
utility method that does this:
Util.loadBead(classOrInterface:Class, strand:IStrand):IBead{
// search for an existing bead
// load it from css if it doesn't exist
// return null or bead
}
--
View this message in context:
http://apache-flex-development.2333347.n4.nabble.com/FlexJS-MDL-Add-icon-to-DeletableChip-tp56766p56808.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
