On 11/30/16, 8:24 AM, "piotrz" <piotrzarzyck...@gmail.com> wrote:
>Alex, > >By "Merge Bead" I mean scenario where one bead needs the second one, so >I'm >taking both in order to produce some HTML content. Could it make sense >also >for non MDL components ? I haven't looked at this Chip component very closely. I can't tell if the DeletableChip and a MaterialIconCancel bead could both be considered content for the View or if DeletableChip is the view. Either way, in my mind, a "merge" would mean that APIs on one bead would consider the other bead, just like if you actually merged the source code before compiling. The principle that beads need to work together is certainly true outside of MDL. The principle that two beads are essentially representing content should also apply outside of MDL. I'm just suggesting that you come up with a better name that more specifically defines what the conversation between the beads are. Maybe the view bead needs to scan the strand for multiple beads that support a new interface called IContentBead or something like that so that the text or html content of some HTMLElement can be specified as beads in a particular order on the strand, just like you would place in-line html tags. HTH, -Alex
