Hi Carlos, The one think which come up to my mind are interfaces. What if your new model - bead - will have different interface implemented. Adding it by addBead should work...
Piotr On Tue, Oct 23, 2018, 12:14 AM Carlos Rovira <[email protected]> wrote: > Hi, > > I'm using the bead system a lot in my app, and is very powerful, but I have > some case that I'm not sure how to deal with: > > Let's say I migrating some business logic separated in different classes > for example some Model classes (IBeadModel), some controllers > (IBeadController) > that manages the business logic of the application and communicates with > the server. I'm configuring those beads through CSS > > Many times, one component, form or view (here the strand) has one > IBeadModel, and one IBeadController among other beads, but other times a > the strand would need more than one IBeadsModel and IBeadController (so a > for example a view is managing more than one entity and its relations so > each entity is separated in different classes as usual), and I think if I > setup a bead of a concrete type and then use "addBead" to add other, the > latest removes the older one. So we can't have mode than one bead of the > same type. > > Is this right? If so, how to deal when we have more than one bead of the > same type and we want to access any of them? > > -- > Carlos Rovira > http://about.me/carlosrovira >
