I just saw how ugly the variabled names in freevo_config.py are. It's hard to see a pattern, it's not clear which variable belongs to what part of Freevo.
Yes, it is nasty!
So I suggest the follwing renaming (will break most local_conf.py, but sorry):
Global Freevo variables should start with the location they are used, like OSD, DIRECTORY, ROM_DRIVE, e.g. OSD_STARTFULLSCREEN, MENU_CONFIRM_SHUTDOWN, MIXER_CONTROL_ALL_AUDIO.
After that, we have same stuff only for video, audio, etc. So they start start with VIDEO and than their context, like VIDEO_MPLAYER_SUFFIX, AUDIO_XINE_SUFFIX, etc.
This will be a big and ugly change, so what do you think?
I think we should find a new config file format. I would like to see us move forward with an XML based config. This kind of config could be loaded into any sort of frontend easily and is still human readable for manual configuration. XML will also help us deal with the increased complexity of our config, and I have some changes that will make it worse.
I don't use XML a whole lot but I see how it could really help us out here! Unfortunately I don't have a lot of time to put into this part of the project.
-Rob
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
