tag:blogger.com,1999:blog-5582430206568048549.post9221267488190520059..comments2008-06-22T04:42:45.617-07:00Zhang Shunchanghttp://www.blogger.com/profile/11799941116002120033noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-5582430206568048549.post-7644899422316383112008-06-22T04:42:00.000-07:002008-06-22T04:42:00.000-07:00to:mpt<BR/>There are two checkboxs at the menu of new mail composer. You can choose to encrypt or sign the msg.<BR/><BR/>Thanks for your suggestion. If your have any good idea for improvement of evo, please let me know.:)Zhang Shunchanghttp://www.blogger.com/profile/11799941116002120033noreply@blogger.comtag:blogger.com,1999:blog-5582430206568048549.post-79827579088935888812008-06-21T23:59:00.000-07:002008-06-21T23:59:00.000-07:00While you’re replacing that section, I wonder if you might be interested in fixing a couple of design problems in that section of the dialog.<BR/><BR/>It’s bad for a checkbox to have a label starting with “Always”, because that means it’s not clear what happens when the checkbox is unchecked. Here, what happens when “Always sign messages when using this account” is unchecked? Does Evolution sign messages just sometimes? When? Does it ask you when you click Send? Or do you have to choose a menu item? Or what? The other two checkboxes starting with “Always” have the same problem.<BR/><BR/>Usually the way to solve this is to replace the checkbox with a pair of radio buttons. For example, “Sign messages sent from this account: (*) Always ( ) ________”.<BR/><BR/>It’s also bad for a checkbox to have a label starting with “Do not” (or “Don’t”, or “Never”), because it’s back to front, so it’s harder to understand what it does. Here, “Do not sign meeting requests (for Outlook compatibility)” would be better as “Sign meeting requests (doesn’t work with Outlook)”.mpthttps://login.launchpad.net/+id/BBLLXTmnoreply@blogger.comtag:blogger.com,1999:blog-5582430206568048549.post-40522273260639308482008-06-21T09:13:00.000-07:002008-06-21T09:13:00.000-07:00hey!<BR/><BR/>disclaimer: I'm not someone who has read the evo code<BR/><BR/>I believe all your questions would be answered by changing the approach of your work: instead of writing a separate plugin, you should really be writing a patch for the current implementation<BR/><BR/>this means you'd also be extending the EAccount structure to hold the new data you need to saveGustavo Noronhahttp://www.blogger.com/profile/17699960458897502930noreply@blogger.comtag:blogger.com,1999:blog-5582430206568048549.post-15547468636355487992008-06-21T05:01:00.000-07:002008-06-21T05:01:00.000-07:00Awesome work! But I also wonder how that should fit on my screen. Maybe having subtabs, but that's also evil...<BR/>Well, still some time left until UI Freeze for GNOME 2.24 takes place. ;-)andrehttp://www.blogger.com/profile/02875987414823165316noreply@blogger.comtag:blogger.com,1999:blog-5582430206568048549.post-90155236410494828852008-06-21T00:30:00.000-07:002008-06-21T00:30:00.000-07:00so i want to hide the original GPG frame :)<BR/>but i have no idea about that.Zhang Shunchanghttp://www.blogger.com/profile/11799941116002120033noreply@blogger.comtag:blogger.com,1999:blog-5582430206568048549.post-31568027359258787882008-06-21T00:23:00.000-07:002008-06-21T00:23:00.000-07:00Wow, does this even fit on an 800 pixel tall display? It looks enormous.Petehttp://www.blogger.com/profile/08412350992799282198noreply@blogger.com