On 7/6/14 10:27 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote:
> >Things like public Atom, RSS feeds do require XML processing. I would assume someone has successfully handles RSS in JS already, probably by using whatever XML apis are there. And that is always an option, but I believe Flash and JS XML APIs are different enough to make that a painful cross-compile. But attempts at that are welcome as well. >Another >scenario is where I wanted to try out my hand at exporting an Adobe >Illustrator file to .FXG. Now that the Creative Cloud extensions are >HTML(5) based, that seems like a good target for FlexJS. Thanks for reminding me to ping the CC Extensions folks after we ship FlexJS 0.0.2. I talked to them a while ago and they are interested. Harbs was the first person to pose the idea to them. > >> >> For others who really truly can't port the backend, it might be worth >>the >> time to convert from XML to Object, similar to the way the SOAPDecoder >>and >> XMLDecoders work today. XML has always been much slower and memory >> intensive in Flash and often folks convert to classes/objects. FlexJS >>has >> support for that already, although there is no generic SOAPDecoder or >> XMLDecoder. >> > >I think mx.rpc.xml.SimpleXMLDecoder should lend itself to FlexJS quite >well. Not exactly E4X, but at least it brings makes it closer to JSON. >What do you think? I think it might have some ties back to RPC, but yes, I would envision a "convert all" decoder like that, plus a "lazy" decode. I've seen the "convert all" freeze Flash for certain XML data sets. -Alex
