--- In flexcoders@yahoogroups.com, "Tracy Spratt" <[EMAIL PROTECTED]> wrote: > > "...it must enter this method as an XMLNode.." Can you explain why that > is so?. The XML API is much more powerful than the obsolete classes. > True it lacks a few convenience properties/ methods like "nextSibling", > but these are easily added. I just want you to be sure of your choice, > because I think you are hitching your wagon to a near dead horse. > > > > Also, you DO have a root node in your xml, you just chose to not have > one in your XMLListCollection. > > > > But if you are happy, I'm happy. > > > > Tracy >
Indeed, I am happy enough - it works for all I need it to do. FYI, the reason for using the older XML stuff is exactly what you have said - missing firstChild and nextSibling etc. I have actually converted a bunch of c#.NET code that uses WPF and XAML to consume my Web Services into AS3, and the patterns inside that code rely heavily on firstChild / nextSibling. The transition has been almost line-for- line and works very well, so I dont want to change any interfaces/algorithms at this point. And I do like the way the tree renders with no root item - I am still wondering if the default getChildren() implementation is broken as I can not seem to begin navigating the tree with no root. Cheers, Radek
