>> >> 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. Well, I'm still planning on "addElement" instead of "addChild" so I don't have to wrap addChild in containers, but you should be able to more easily re-route addElement to Starling's addChild. And I think it would be easier to get addElement to understand the child is a Starling object than to try to add an addToParent onto every Starling class.
I'm going to start changing over the code. It will probably take until tomorrow so everyone has plenty of time to continue to discuss in this thread. Thanks everyone for your input so far, -Alex
