I’m glad you liked it. All my code on my blog is free for anyone who wishes to use it.

- Mike

I’m glad you liked it. All my code on my blog is free for anyone who wishes to use it.

- Mike

http://iainmclaren.com/2010/02/26/pdialog-create-a-preferences-dialog-box-using-a-simple-text-file/

Basically, I have added file and directory downloads (and used a wx.FlexGridSizer to line up the columns).

Thanks

Iain

http://iainmclaren.com/2010/02/26/pdialog-create-a-preferences-dialog-box-using-a-simple-text-file/

Basically, I have added file and directory downloads (and used a wx.FlexGridSizer to line up the columns).

Thanks

Iain

Thanx for following up on my feedback so quickly. I like your solution.

The original idea behind this was that typically, as a pythonista, you have a couple of useful programs that are called from the command line (be it Linux, some other flavor of Unix, or Windows). But if you are on a system with a graphical ui, you want to offer the user the same functionality but with more comfort.

One could subclass the ConfigObj, and this subclass either just goes ahead and reads the config file, or — if in a UI environment — displays the preferences panel, and returns as soon as the user has clicked on ok. And/or one combines it with an OptionParser (for the non-ui case) that allows the user to override the preferences from the config file.

ideas over ideas

But thanx again!
Axel

Thanx for following up on my feedback so quickly. I like your solution.

The original idea behind this was that typically, as a pythonista, you have a couple of useful programs that are called from the command line (be it Linux, some other flavor of Unix, or Windows). But if you are on a system with a graphical ui, you want to offer the user the same functionality but with more comfort.

One could subclass the ConfigObj, and this subclass either just goes ahead and reads the config file, or — if in a UI environment — displays the preferences panel, and returns as soon as the user has clicked on ok. And/or one combines it with an OptionParser (for the non-ui case) that allows the user to override the preferences from the config file.

ideas over ideas

But thanx again!
Axel

You could even go as far as creating separate ConfigObj sections for each preference, containing things such as widget type (checkbox/radio), label, tooltip etc

Taking actions such as updating the GUI based on the new user’s preferences can easily be done in the OnSave method by maintaining a copy of the (application’s) configuration file in the Preference class, and checking its new values against the original config file. You could, for example change the font by doing:

if old_config['font'] != new_config['font']:
self.update_font() # or something

if config['show_statusbar']:
self.show_statusbar()
else:
self.hide_statusbar()

if config['show_toolbar']:
self.show_toolbar()
else:
self.hide_toolbar()

hope that makes sense

You could even go as far as creating separate ConfigObj sections for each preference, containing things such as widget type (checkbox/radio), label, tooltip etc

Taking actions such as updating the GUI based on the new user’s preferences can easily be done in the OnSave method by maintaining a copy of the (application’s) configuration file in the Preference class, and checking its new values against the original config file. You could, for example change the font by doing:

if old_config['font'] != new_config['font']:
self.update_font() # or something

if config['show_statusbar']:
self.show_statusbar()
else:
self.hide_statusbar()

if config['show_toolbar']:
self.show_toolbar()
else:
self.hide_toolbar()

hope that makes sense