Originally posted by Tupps
If you are running the XML locally there is a back door that allows you to save files using the fscommand function, however it is not documented and only supported on the PC.
This is exactly what I want to do. I'm making a stand-alone Flash app, and exercise log. I want to keep track of progress, groups of exercises, etc.
I'd like more info on this 'backdoor' fscommand function, please!! Actually there are a lot of apps I'd like to develop with Flash. It is just a lot easier than C++ or Delphi.
Oh I would also like to know what is this backdoor if theres one.
But you have a chance to write data on users computers use localSharedObject it's like cooky on users machine.
Through a little meta-searching I found that you do it like this:
fscommand ("save","file.txt")
But I would like to save into an actual XML file. Actually, I'm not sure if XML or just a text file with variables is necessary. For instance, with XML I could create something like this:
For info on localSharedObject, go to http://www.flashworker.de/tutorial/40/001.html . It's not in English, but you can understand it. LocalSharedObject is the Flash version of cookies. It saves in files, though. This page/tutorial should answer your question.
Seriously, is this a viable path or are we making things harder than they are? Macromedia has no support pages for localSharedObject. I only found the link posted above when I searched for it on Google.
Found many pages that said the save fscommand is a major vulnerbility threat. But Windows (Not Mac OS X, Linux, or other UNIX flavors) is the only OS vulnerable to this fscommand. It appears to work only on the PC. Windows is insecure to everything. I can create a JavaScript that grabs all your personal information from Outlook. I've never got a virus on my Mac, either, nor have I ever been hacked. The Mac will tell you when stuff like this happens, although it rarely does happen and requires you to use the Terminal or an access blocker like BrickHouse. Or Virex, Viruscan, etc.
Anyway, back to the save FSCommand. It only works in Windows projectors.
I also seem to remember that some (all?) MX projectors on FlashMX no longer support this. It is undocumented, which means that Macromedia might disable this feature at any time.
If you are using FlashMX look at the local stored objects.