If we can do it in some sort of transitional way, or even just a "migration" script that copies them over to a new file, it would make life a lot easier.
On Sat, Nov 22, 2003 at 04:36:36PM +0100, Dirk Meyer wrote: > Hi, > > 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. > > 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? > > > Dischi > > -- > Unnamed Law: > If it happens, it must be possible. > > > > ------------------------------------------------------- > 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 ------------------------------------------------------- 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
