Rick Gruber-Riemer wrote: > I wanted to use the latest and greatest of Chandler to get started with > writing a plugin (which in the end should store secret/encrypted > personal information like login infos to different web-sites). So I got
Just pointing out that it is possible to encrypt the whole Chandler repository (there is an optional startup argument for this) and account passwords in Chandler today. Plugins that add new kinds of accounts also have access to the password encryption functionality, take a look at the gdata plugin for example. > Having looked at Chandler from a plugin perspective only the last few > days and being a novice to Python, I do not know, whether the > re-creation of the repository was a "natural" thing to do. Therefore I > suggest that BuildingChandlerDesktop eventually gets a note about having > to re-create the repository in some situations. --create should not be needed (Chandler should automatically notice schema differences) unless developers made a mistake and forgot to update the schema number. I added a Troubleshoot section on the build page to address this and another kind of common problem. -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
