It did not work as well as I originally thought, but it’s working now. Modifying XMLList should now effect the original XML as well.
There’s one caveat: It seems like according to the spec, the original object of an XMLList can be another XMLList which recursively works its way back to an XML object. I cannot think of a use case for this, and I took they easy way out for now assuming that the source object is always an XML object rather than an XMLList object. I someone knows of use cases for the speced behavior, please let me know. I also merged the e4x branch onto develop and I’ll be working off develop from now on. Running ant on FlexJS will build XML (minus the SWC) along with the rest of the projects. On Apr 10, 2016, at 7:46 PM, Harbs <harbs.li...@gmail.com> wrote: > I just added a test for indexed insertion of items in an XMLList and it works > perfectly. I’m surprised it worked on the first shot! > > I need to get the syncing of the original XML object working though. > > On Apr 10, 2016, at 4:02 PM, Harbs <harbs.li...@gmail.com> wrote: > >> I reached a milestone today with E4X. I have the first working test which >> reads an XML literal, writes it back out to a string and writes the value of >> an attribute using E4X notation in Javascript! >> >> Over the next couple of weeks I expect to be fixing a lot of issues related >> to XML and the better the test-case coverage we have, the better the quality >> will be. >> >> I’d like to put out a call for snippets of E4X code that people are using in >> the wild so we can incorporate tests for as many use cases as we can get. >> >> If you have code snippets to contribute, please respond! >> >> Thanks, >> Harbs >> >> (P.S. There is currently a compiler issue with two of the XML methods, so >> the XML.js file needs a bit of editing before it can be used. Hopefully this >> issue will be fixed soon.) >
