Also you can enable user to save file on their local hard drive via using FileReference class. This though doesn't have any access to file structure - it behaves exactly like when you save, say, image from a web page with OS' interfaces etc.
You can ALLOW USER save it with FileReference. Other wise, unless it is an air application - you cannot save anything on user's harddrive without him being aware that it was saved. SharedObject is, of course, an exception but it is a slippery road because user can always reject/remove this info.
How are you going to reuse this saved file if ever?
It will be the way for the site to access the information concerning their particular dragon each time they log on. That way the information can be concerning their particular dragon and I do not have to keep a large amount of information on the server for each member.
Here is documentation for SharedObject:
Also there are tons of tutorials on Internet on how to use it. Here is the first one that comes on Google:
var so:SharedObject = SharedObject.getLocal("yourso");
// use so.data.whatevervariable etc
// some place when you have the data that's needed to be saved:
no, you don't have to apply the flush() method to write to your so. if you apply flush(), data is written to the so immediately. if don't apply flush(), data is written when your swf closes.
p.s. i notice you marked many of your threads as answered but gave noone credit for giving a helpful or correct response. if someone gives a helpful/correct response, you should mark their response.
Just so taht you know, many of the items I marked as answered were because I got them answered by doing a lot of research elsewhere and finally coming up with the answer. I gave credit where credit was due.
Europe, Middle East and Africa