Initial checkin of supybot-based config method

- this simply proxies all string attributes of the Config class to the
  supybot config namespace supybot.plugins.MeetBot.*  When you adjust them
  in supybot, the MeetBot methods see the changes.
- To enable, you must set supybot.plugins.MeetBot.enableSupybotBasedConfig
  to True, and then reload MeetBot.
  Then "config list supybot.plugins.MeetBot" and you'll see a bunch of
  variables for you to change.
- To-do: think about supybot config stomping changes to defaults, and
  implement channel-based config.

darcs-hash:20090626184017-82ea9-c24fcb02c54fd848de6ce5b212b1a48fcf42d970.gz

1 files changed, 4 insertions, 0 deletions

diff --git a/config.py b/config.py
index 734294b..911cbb2 100644
--- a/config.py
+++ b/config.py
@@ -44,6 +44,10 @@ MeetBot = conf.registerPlugin('MeetBot')
 # This is where your configuration variables (if any) should go.  For example:
 # conf.registerGlobalValue(MeetBot, 'someConfigVariableName',
 #     registry.Boolean(False, """Help for someConfigVariableName."""))
+conf.registerGlobalValue(MeetBot, 'enableSupybotBasedConfig',
+    registry.Boolean(False, """Enable configuration via the supybot config """
+                            """mechanism."""))
+
 
 
 # vim:set shiftwidth=4 tabstop=4 expandtab textwidth=79: