Title: is "delete" really the best/only way to remove a node in e4x?
For native Flash Player APIs, I'd log a bug against the
player... this isn't really a Flex decision.
From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Tracy
SprattSent: Wednesday, May 24, 2006 9:29
Title: is delete really the best/only way to remove a node in e4x?
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
Title: is delete really the best/only way to remove a node in e4x?
The E4X standard allows the addition of
APIs in certain circumstances, but not this one. The standard explicitly prohibits
the addition of methods to the XML or XMLList prototype objects, which are where
the other methods
Title: is delete really the best/only way to remove a node in e4x?
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: flexcoders@yahoogroups.com
Title: is delete really the best/only way to remove a node in e4x?
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
Title: is delete really the best/only way to remove a node in e4x?
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.
Tracy
From: flexcoders@yahoogroups.com
6 matches
Mail list logo
