Re: Passwords and so

[Karol Będkowski <karol bedkowski gmail com>]

Hello, 

2010-01-20 19:11:36 Ulrik Sverdrup <ulrik sverdrup gmail com>:
>Karol, I'm not reading all your ongoing google plugin stuff, but I
>will later if you want me to. 

Of course, your comments are very helpful. Thanks for your previous
advices.

>We need to store user credentials. I imagined we could rely on
>something like python-keyring in this case: it's a library that
>abstracts access to the user's installed keyring. (It says it supports
>Gnome Keyring and KWallet right now). I'm not sure if it has a
>fallback if no keyring service is found. Using that, we can store the
>password in the keyring and password safety won't be our problem and
>the user will feel safer.

Yes, I thinking about it. For now I store password in plugin
properties, but my changes are (for now) only proof-of-concept.
Without any keyring, we should provide at least something like
base64 encoding for passwords. Gnome Keyring is IMHO best solution. 

>Custom preferences: There is no method for this now, but it should be
>made possible for the plugin to pass a gtk Widget object to the
>plugin_support.PluginSettings object. Kupfer will then display this
>widget in place of the normal configuration widgets. The widget can be
>just a button to launch another window under the plugin's control
>("Set User Credentials").

I agree. We can provide some standard widgets (like credentials). But
some plugins need more "advanced" settings. So maybe plugins should
have something like __kupfer_preferences__ property for name of
configuration widget class.

>When the google plugin doesn't have credentials from the keyring/ the
>credentials are invalid, it should just insert a "Please configure
>user credentials" object into the catalog. When run this object should
>open the preferences window for the right plugin
>(kupferui.show_plugin_info(..)).

Ok, I will update plugin.

Regards,
Karol