Hi Kent, The other way to export XML would be to use a SWF wrapper such as mProjector, SWFStudio or (open-source) SWHX: http://www.haxe.org/swhx. (Zinc is another alternative, but I can't recommend it - I've had all sorts of stability issues with it.)
Alternatively, Apollo (from Adobe) will be out sometime this year. Basically all these tools provide a container for a Flash app that lets Flash request writing/reading of external local files (amongst many other features). Hope that's helpful, Ian On 3/19/07, kent humphrey <[EMAIL PROTECTED]> wrote:
For an upcoming project, I have to investigate whether to use a shared localobject for storing user data, or exporting XML. This is for a cd based app, not a website. A shared localobject would be my first choice, except that we want to be able to access the saved data from a second release of the cd. My understanding of the security of local objects is that they are only accessible from the app that created them. Is that correct? Or is it possible to work around that? If the second release would not be able to retrieve the data, I thought maybe exporting XML would be an option. But from my searches, all the ways of doing that involve sending to a server, and we wont be able rely on net access being available. Are there any other ways of exporting xml? Or is there a method I haven't thought of? The basic requirement is that user data can be saved to the local machine, and then read in again by the same app, and any other subsequent apps. Ideally we don't want to have to do a local install, but would consider it if there is no other way. Thanks for your time.
_______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
