Eric Bus wrote:

Richard van Paasen wrote:

Instead, all modules should be extended with a 'reconfigure' method that is
called after a (set of) config setting(s) has been changed.


And I guess the config file should be written in a 'plain-text' format, like XML, so Freevo can reload it while running.

Eric

XML would be fine if ALL configuration could be done via interface, some setup. It is better format for our Freevo machines ;)

However, if _some_ parts of config should be done still in vi (nano, ..your fav editor) it would be IMHO better to keep the config file the way it is now -> more readable for humans. Also, if someone omits/accidentally deletes XML closing tag for example...all XML parsing goes to hell.

Dale





-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users

Reply via email to