On Jul 16, 2013 9:34 AM, "Alex Harui" <aha...@adobe.com> wrote: > > > > >> > >> Removed initModel and initSkin methods. The lifecycle is now much > >simpler: instantiate, set properties and beads then add to the display > >list. We're still using child.addToParent(parent), but I am going to > >experiment next with changing over to parent.addElement(child). > > > >Any particular reason why? I was beginning to get a hang of the > >child.addToParent() way. > > The short answer: to reduce migration pain. My internal customer showed > me a bunch of code with a lot of addElement() calls in it.
This is a great reason :-) I am for making it easier for existing apps to port to FlexJS. > > The long answer: I was looking at how addToParent() is currently > implemented and found that I couldn't completely remember why I felt it > was a better strategy. I remember a conversation about trying to move away from the traditional display list approach so that we are not overly dependent on the Flash player way of doing things. Also there was a talk about ASNext which was also planning on removing the display list (which is no more the case) I am not 100% sure yet, but I believe that bringing back addChild() might make it easier for us to make FlexJS work well with Startling at least. Thanks, Om
