Is this useful? http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/utils/XMLNotifier.html#watchXML%28%29
On May 13, 2016, at 9:18 AM, jude <flexcapaci...@gmail.com> wrote: > Is the MXMLLiveEditAgent.mxml the only place those methods are from? I > thought I read somewhere that you copied those methods from somewhere else. > I'm trying to find the class that those methods were originally in to learn > how to parse an XML tree and then track it's changes as if a user was > updating it constantly in an editor. I looked at the MXMLDataInterpreter > but that looks like it's for importing. > > OK, I think here is where I got the idea. The comments are from > MXMLLiveEditAgent.mxml: > > // we go deep first because that's how the Falcon compiler > // generates IDs for tags that don't have id attributes set. > > I'm guessing that the methods are from or inspired from a class in Falcon? > That class or code is what I'm trying to find and learn from. > > > On Thu, May 12, 2016 at 11:08 PM, Alex Harui <aha...@adobe.com> wrote: > >> >> >> On 5/12/16, 5:31 PM, "jude" <flexcapaci...@gmail.com> wrote: >> >>> I read somewhere, and it might have been the code comments, that you used >>> some code from mxmlc or maybe it was an class used in Eclipse MXML class >>> to >>> parse the MXML and compute the changes for your live MXML PoC. I'm trying >>> to find the class that had the following functions: >>> >>> parseFile(); >>> computeChanges(); >>> applyChanges(); >> >> In my POC, the MXMLLiveEditAgent has those methods. >> >> The MXML parsing is done by the XML class. >> >> I think you may be thinking of the MXMLDataInterpreter, and how the Falcon >> compiler outputs MXML as an array to be interpreted by the >> MXMLDataInterpreter (as well as the MXMLLiveEditPlugin) instead of a pile >> of one-off methods that are not manipulatable at runtime. >> >> -Alex >> >>
