GNOME Bugzilla – Bug 342296
mail-to-memo
Last modified: 2009-04-27 12:32:27 UTC
- right click on mail message to create memo from message (mail-to-memo) - right click on task to send it in a mail (task-to-mail) - right click on memo to send it in a mail (memo-to-mail) - export evolution profil (mail + memo + contact + task + calendar + gconf setting). Actualy, I use a bash script. You can download him here. - add RSS reader component (to read news in evolution).
Created attachment 65792 [details] My evolution backup script
uhmm... these requests are partially already filed into bugzilla, and they can much better be handled if you file seperate enhancement requests. - mail-to-memo does not exist yet, right. however, how should this work? - you can forward any memo/task as an icalendar, so this is already possible in evo 2.6 (if you have enabled the plugin). - i'm 100% sure that "export evo profile" is already filed in bugzilla. - an rss reader already exists, it's called evolution-brainread iirc. this will not become part of the evolution codebase as there is no-one who would maintain the code. once upon a time, evolution had an rss reader included, and it was removed for that reason. therefore changing the subject, please elaborate a bit what you would expect exactly from such a function.
- i'm 100% sure that "export evo profile" is already filed in bugzilla = OK - an rss reader already exists, it's called evolution-brainread iirc. this will not become part of the evolution codebase as there is no-one who would maintain the code. once upon a time, evolution had an rss reader included, and it was removed for that reason = OK - mail-to-memo = just send a mail with the memo content - you can forward any memo/task as an icalendar = ok, but I can't forward memo/task as an mail. Example, I am a manager, and I want to send a task to an employe. I Write a task and forward it.
sebastien, for your interest: perhaps we will get evolution-brainread into 2.8, see bug 343029. "but I can't forward memo/task as an mail." - why would you? so you want a "plain text" output like Summary: bla Description: bla ? if you're a manager who wants to send a task to an employee, you will just send a task attached to an email, as probably both people will use the same email/task application in that company. so does evolution. ;-)
Created attachment 85486 [details] mail-to-memo.c concerning the current summary of this bug, I've done some work based on mail-to-task plugin to get a mail-to-memo working. Afaics, it does the job (attachments included) which is exactly what I wanted it for. I don't know exactly how to handle the authors assignement so please fix it if it's wrong. The plugin is mostly a copy/paste of the mail-to-task plugin.
Created attachment 85487 [details] org-gnome-mail-to-memo.eplug.xml additional file for the plugin.
Created attachment 85488 [details] org-gnome-mail-to-memo.xml last piece of the plugin. You'll need to check that mail-to-memo is inserted in configure.in for it to work. I can provide a patch if necessary.
ok, after some more testing, it appears that setting Organizer for a memo is not a good idea. Removing set_organizer and subsequent call fixes it. I'm now looking into finding how to set the memo "start date". Not sure if this would be meaningful but at least fonctionnality would be "complete".
Created attachment 124426 [details] [review] proposed evo patch for evolution; As we settled with Gilles, stealing this bug to extend mail-to-task plugin to be able to create any type of the event. This obsoletes mail-to-memo plugin, which should be removed from svn in time of the commit. Things I changed: - calendar events are created as all day events, (because it's easier than looking for calendar's timezone and so on). - others has setup only start day. - the start day is chosen as today, the day when user invoked the action - organizer is set to the user itself, not to the "from", because he/she should be able to do changes in the event - organizer is never added to the attendees' list And that's all I think. Enjoy.
*** Bug 420517 has been marked as a duplicate of this bug. ***
Created commit 96a85a6 in master.
*** Bug 580173 has been marked as a duplicate of this bug. ***