On 12/31/16, 8:52 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> wrote:
>Hi Alex, > >although I think that is a valid approach for other of components, I think >this is not in this case. Imagine users need to extend lots of containers >to append html text. I don't think that as an easy way. For that reason I >use to discuss with you how to do that. > >In use cases where the need is isolated and focused only on that case, I >think that's the way to go, but considere how many MDL containers we >hace....that approach would be very cumbersome for final users. > >For example in Grids.mxml I have > ><mdl:GridCell column="1"><mdl:beads><js:InnerHTML >text="1"/></mdl:beads></mdl:GridCell> > >Just to output a "1" inside a div. I think that, although more verbose is >the way to use in final app.For that case in particular... Well, IMO, we are in the business of looking for patterns and encapsulating them into components. The whole point of composition is, once people get tired of typing "js:InnerHTML text=" that someone, maybe us, will publish a component that is GridCell with InnerHTML via a text or html property, just to save typing. Can't really prevent it. That said, it might be worth revisiting whether we can create non-IUIBase children in the default property for Containers. We can probably modify the compiler to do it, but then components that need to handle mixed content have to have code that checks for mixed content which slows up startup time when lots of children are being created and added. Thoughts? -Alex
