|
It may not be a Flash decision either
since the API of the XML class is specified by the E4X standard. It would
depend on whether that standard allows an implementor to add additional APIs or
not. - Gordon From: For native Flash Player APIs, I'd log a
bug against the player... this isn't really a Flex decision. From: I am not really fussing very hard, it is
just that we have: XML.appendChild() XML.insertChildAfter() XML.insertChildBefore() XML.prependChild() but no XML.removeChild? delete is a completely different style
syntax. From: I don't know whether it is the best or
only way, but it seems consistent with the use of the 'delete' operator to
remove a dynamic property of an Object. - Gordon From: If
this is the final API, I can deal with it, it is just
inconsistent and undocumented, and a bit of a shock when the rest of the api is
so clean and logical. I
admit I have not read the e4x specification.
|
Title: is "delete" really the best/only way to remove a node in e4x?
- RE: [flexcoders] is "delete" really the best/only... Gordon Smith
- RE: [flexcoders] is "delete" really the best... Francis Cheng
- [flexcoders] The Kiwi project (cool new app and re... David Mendels
- [flexcoders] Max 2006 Darren Houle
- RE: [flexcoders] Max 2006 Joan Tan
- RE: [flexcoders] Max 2006 Ben Forta
- RE: [flexcoders] Max 2006 Darren Houle
- [flexcoders] Re: The Kiwi project (cool new ap... dirtmediaworld

