Re: [Flashcoders] shared local object, or XML export? or other?

2007-03-19 Thread Chris Tague
You could always use one of the flash wrappers that give you access to the filesystem, which would allow you to write files to the users drive, somehting like zinc. I think, although someone can confirm this that the shared object can be accessed by a second app if the name of the app is the

Re: [Flashcoders] shared local object, or XML export? or other?

2007-03-19 Thread Chris Tague
forgot the link to zinc.. http://www.multidmedia.com/ On 3/19/07, Chris Tague [EMAIL PROTECTED] wrote: You could always use one of the flash wrappers that give you access to the filesystem, which would allow you to write files to the users drive, somehting like zinc. I think, although

Re: [Flashcoders] shared local object, or XML export? or other?

2007-03-19 Thread Ian Thomas
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

RE: [Flashcoders] shared local object, or XML export? or other?

2007-03-19 Thread Karina Steffens
I would definitely go with shared object. You can access it from whatever app you like if you pass a local path parameter, like this: so = SharedObject.getLocal (mySharedObject, /) so = SharedObject.getLocal (mySharedObject, /myProject) Etc... If you don't pass the path, it generates a local path