A further note: Normally, we will use
XMLListCollection to manipulate dataProviders, and that interface DOES have a
removeItemAt(), so this is again not a big deal. 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... Tracy Spratt
- RE: [flexcoders] is "delete" really the best... Peter Farland
- RE: [flexcoders] is "delete" really the ... Gordon Smith
- RE: [flexcoders] is "delete" really ... Francis Cheng
- [flexcoders] The Kiwi project (cool new ap... 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 (co... dirtmediaworld
- [flexcoders] Re: The Kiwi project... bringrags