Hello Rob, Monday, February 19, 2007, 7:20:37 PM, you wrote: RS> No, I wanted to make the user config file more easily edited by hand, RS> so I didn't use XML for it. Most normal people find XML too complex and RS> verbose.
Exactly. And that's why I'm surprised that you're suggesting XML for a configuration file. RS> You can look at the XML.as and XMLNode.as testcases for how to RS> use XML, plus it follows the Flash spec as well. Basically each node RS> becomes an object in the Flash VM, which you can walk through using RS> ActionScript to extract the settings. Don't understand why you're talking about ActionScript - the GUI is not related to the VM. Hmm, I think you confused something. :) The configuration file we're discussing is *completely* unrelated to the movie. The movie may be some .swf file downloaded from the net and *not* specifically designed for Gnash. However, for the player to work correctly, some additional configuration is needed to support the hardware. This is something the user has to do - just like he has to configure it's X server. RS> Since I think you're embedded Gnash onto your own hardware, RS> using an extended Gnash is totally acceptable, so just reading a simple RS> file of any kind would work. I basically agree with you, but the FB GUI is not an extension - it's a choice. RS> This is one of the main reasons I added the File I/O extension. For RS> embedded platforms, better access to the hardware makes total sense as RS> long as you can do it in a secure manner. Fully agree! I'm happy you made this extension, as otherwise I would have to do it :) I'm missing functions like rename(), though. Using files is the most simple and effective way to talk to the rest of an embedded system. As for compatibility, is there a way to detect if the file I/O extension is available? Udo _______________________________________________ Gnash-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-dev
