The first two choices are pretty much the same thing, just different ways of selecting the nodes in the first place. Once you have them, it's still a bit of a pain to replace nodes.
The best solution is probably XSLT, depending on how complex the transform that you actually want to do. It could just be overkill. I am planning to build a full XSLT implementation at some point, but it won't be any time in the next few months unless there are volunteers... Peter On 10/8/07, Alias™ <[EMAIL PROTECTED]> wrote: > Hi guys, > > I'm wondering if anyone has any opinions on this. I'm faced with the > need to search and replace a bunch of XML tags in an AS3 project. The > tags are going to be nested, and will probably be basic HTML elements, > and replacing them with other html elements. For various reasons it > seems that this is necessary because of the project's localisation > goals. > > I'm currently considering the following options: > > - native E4X > pros:built in, simple > cons:not really powerful enough without writing a lot of code > - the memorphic xpath library (http://www.memorphic.com/news/?page_id=16) > pros:xpath is nice and what I'm used to > cons:might be using a sledgehammer to crack a nut > - native regex: > pros:built in, lots of prewritten magic regexes which could do the job > cons: lots of prewritten magic regexes which could do the job, > but might also mysteriously fail further down the line > > Has anyone had any experiences with this that they'd like to share? > > Thanks in advance, > Alias > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
