Week 9 progress update

There was a bad luck with me last week. my OpenSuSE Linux broke down when i changed a CPU. so i updated the system to a higher version(OpenSuSE 11.0), which works well till now, but the bad news is my private GnuPG key was lost, 'cause i didnot backup my data in the root directory(it is a bad habit using the roor user).
After some configuration(such as installing Pidgin,Stardict; highlighting GTK+ syntax in Vim, .etc), the work evironment is ok now, the nightmare has gone.

Howerver, there are some good news, such as most of my codes is in my SVN repos, so the lost was very little; and i find a bug in my codes with the new environment and it is fixed now. Besides i reconstruct my UIs according to the feedback from my soc blog. please see the following snapshots:

i add another configuration dialog for GPG Key selection, although there is few people using more than one GPG Key, we also provides the choice for that case. One can select and apply the GPG Key can sign and encrypt in the GtkTreeView. i borrow the icon file(GTK_STOCK_APPLY ;)) from GTK+ to indicate which key was applied now if exists.

According to Coly Li, a guy from Novell, one usually puts all of his/her email address to a GPG Key, which is also the reason i replaces the combobox with the GtkTreeView(borrow from the Seahorse).
The displays item(name, comments, email)can fold and unfold.

which is activated by clicking the configure button in a newly-added tab page in Account Editor.

So, i would like to manage the certificates as the GPG Keys(adding a button and a dialog).
Please fill free to give me some feedback.:)

Happy Hacking!


week 8

i have no update this week, because i am confusing with my implementaion of the certificates part.
I intended to implement it using gnome-keyring, howerver, it seems that its far away from the topic of my GSoC application:)
i have no idea about the integration of Seahorse and gnome-keyring.

We have a meetup at Google office in Beijing last monday, and some guys give me a lot of useful suggestions. So i thought a lot about that ideas, the UI of GPG Key selection part may be chenged accordingly.

Hope next week there will be some good news.


week 7

this week i did some research about the gnome-keyring's API and wrote some test codes.

Project Progress:
1.diving into the manuals and APIs of gnome-keyring, especially
the section of "Gnome Keyring Certificates and Encryption Keys"
2.contact with my mentor and discuss the implementation of the GPG Key-selection, but have no reply:(

Next week plan
1.do some programming about the certificates management, i would try to implement a draft.
2.research the UI of smime, and begin to thinking about the UI.

Happy Hacking!


weekly report 6

i dive into the gnome-keyring this week, since the maintainer of Seahorse said that the support of
X.509 certificates is in progress. So i decided to use gnome-keyring and Seahorse(?) to manage the certificates
of Evolution.

Project Progress:
1. keep on going with the development of GPG Key selection
(i want to patch the evo rather than an EPlugin, so i can extend the EAccount struct to store some fields i need)
2. diving into the manuals and APIs of gnome-keyring, especially
the section of "Gnome Keyring Certificates and Encryption Keys"

Next Week Plan
1. i will do something about importing the GPG Key in the Message automatically.
2. discuss with mentor and design the certificates management of Evolution, using gnome-keyring

Happy Hacking!