Re: [Evolution-hackers] Mailing list actions bounty

[Not Zed <notzed ximian com>]

On Thu, 2004-09-30 at 19:55 +0200, Meilof Veeningen wrote:
> On Thu, 2004-09-30 at 09:16 +0800, Not Zed wrote: 
> > > >From the discussion I read on the bounty, there was still a bit of
> > > inclarity on where the actions should be: in the message view as in the
> > > mockup with the bounty, in the "Actions" menu as in the text of the
> > > bounty, in the popup menu for messages, or a combination. What's the
> > > current opinion on this?
> > What bug number was that?
> http://bugzilla.gnome.org/show_bug.cgi?id=127518
>
> There was an RFC about this, as well, but it wasn't really discussed:
> http://lists.ximian.com/archives/public/evolution-hackers/2003-December/002025.html
>
> > I think at present it should probably be done via action and/or popup
> > menu; something that can be done using a plugin.  Though a plugin
> > could probably do message header too (although at present it can't
> > really hook into the right place), but the actual mechanics aren't any
> > different either way.
>
> Are you implying the thing should be a plugin? Not knowing much about
> recent Evolution developments, is the plugin system ready enough to
> allow this kind of thing? I wouldn't much like poking around it if it's
> not ready enough yet...
No, i'm saying it must be a plugin, not implying it may be!

It's ready enough to allow what you want here, since all you really need is a menu item to run and a message/address to run against.
> The method the mockup from the bounty suggests would seem like a very
> neat place to put things, so would it be allright to make a hook in the
> Evo code, or should I really stay away from it?
Hmm, from the bounty it just looks like a popup menu to me.  It could go on an email address uri, or just do it on the normal message context popup menu "for now".

It really doesn't matter where it is,  the logic that does it is the important thing and details like how you activate it are really pointless wasting time over right at this point, when there isn't even any code to implement anything yet.

By writing it as a plugin you can test and verify that its going to even work, and then we can worry about customising evolution if we need to fancy-up how it is accessed.

--

Michael Zucchi <notzed ximian com> "born to die, live to work, it's all downhill from here" Novell's Evolution and Free Software Developer