Hi, I always try to extrapolate from what I see people are doing in MDL. I didn't have the time to search too much, but seems people as the perform something dinamic they use the method, so something "external" is done, and that's the same approach I proposed with the static utility class. That class could as well have some param to loop in child elements to make it more usable.
the interface proposed could be another option, is not introducing the bead by default, so is better option, since we don't have the code instantiated at runtime for each component, but adds the code to the class what seems to me not as PAYG as Util. Hope others like Alex could give us thoughs about this since seems each one is very happy with his solution ;) thanks 2017-02-21 19:56 GMT+01:00 piotrz <piotrzarzyck...@gmail.com>: > I went through the comments and I see that voices rather saying that we > shouldn't make automatic upgrades for the components, but since it is not > easy add this ability as an util, maybe we should introduce an interface - > IDynamic with property IsDynamic - setted by constructor or traditionally. > (of course I'm open for naming) > > If user set it we will add Bead appropriately. > > Is it more PAYG ? > > Piotr > > > > ----- > Apache Flex PMC > piotrzarzyck...@gmail.com > -- > View this message in context: http://apache-flex- > development.2333347.n4.nabble.com/FlexJS-MDL-Dynamic-Child- > Problem-tp59595p59726.html > Sent from the Apache Flex Development mailing list archive at Nabble.com. > -- Carlos Rovira Director General M: +34 607 22 60 05 http://www.codeoscopic.com http://www.avant2.es Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la prestación del servicio o información solicitados, teniendo usted derecho de acceso, rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación necesaria.
