[Evolution-hackers] Mailing list actions bounty
Not Zed
notzed@ximian.com
Fri, 01 Oct 2004 15:28:09 +0800
--=-piiOgjaBa5B0UnA8dXMc
Content-Type: multipart/alternative; boundary="=-YfjVIPnl9NaRxzQNVgDv"
--=-YfjVIPnl9NaRxzQNVgDv
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
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
--=-YfjVIPnl9NaRxzQNVgDv
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.5.0">
</HEAD>
<BODY>
On Thu, 2004-09-30 at 19:55 +0200, Meilof Veeningen wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">On Thu, 2004-09-30 at 09:16 +0800, Not Zed wrote: </FONT>
<FONT COLOR="#000000">> > >From the discussion I read on the bounty, there was still a bit of</FONT>
<FONT COLOR="#000000">> > inclarity on where the actions should be: in the message view as in the</FONT>
<FONT COLOR="#000000">> > mockup with the bounty, in the "Actions" menu as in the text of the</FONT>
<FONT COLOR="#000000">> > bounty, in the popup menu for messages, or a combination. What's the</FONT>
<FONT COLOR="#000000">> > current opinion on this?</FONT>
<FONT COLOR="#000000">> What bug number was that?</FONT>
<FONT COLOR="#000000"><A HREF="http://bugzilla.gnome.org/show_bug.cgi?id=127518">http://bugzilla.gnome.org/show_bug.cgi?id=127518</A></FONT>
<FONT COLOR="#000000">There was an RFC about this, as well, but it wasn't really discussed:</FONT>
<FONT COLOR="#000000"><A HREF="http://lists.ximian.com/archives/public/evolution-hackers/2003-December/002025.html">http://lists.ximian.com/archives/public/evolution-hackers/2003-December/002025.html</A></FONT>
<FONT COLOR="#000000">> I think at present it should probably be done via action and/or popup</FONT>
<FONT COLOR="#000000">> menu; something that can be done using a plugin. Though a plugin</FONT>
<FONT COLOR="#000000">> could probably do message header too (although at present it can't</FONT>
<FONT COLOR="#000000">> really hook into the right place), but the actual mechanics aren't any</FONT>
<FONT COLOR="#000000">> different either way.</FONT>
<FONT COLOR="#000000">Are you implying the thing should be a plugin? Not knowing much about</FONT>
<FONT COLOR="#000000">recent Evolution developments, is the plugin system ready enough to</FONT>
<FONT COLOR="#000000">allow this kind of thing? I wouldn't much like poking around it if it's</FONT>
<FONT COLOR="#000000">not ready enough yet...</FONT>
</PRE>
</BLOCKQUOTE>
No, i'm saying it must be a plugin, not implying it may be!<BR>
<BR>
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.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">The method the mockup from the bounty suggests would seem like a very</FONT>
<FONT COLOR="#000000">neat place to put things, so would it be allright to make a hook in the</FONT>
<FONT COLOR="#000000">Evo code, or should I really stay away from it?</FONT>
</PRE>
</BLOCKQUOTE>
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".<BR>
<BR>
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.<BR>
<BR>
By writing it as a plugin you can test and verify that its going to even work, and <B>then</B> we can worry about customising evolution if we need to fancy-up how it is accessed.<BR>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
<TABLE CELLSPACING="6">
<TR>
<TD>
<IMG SRC="cid:1096615358.9716.0.camel@lostzed.mmc.com.au" WIDTH="48" HEIGHT="48" ALIGN="top" ALT="" BORDER="0">
</TD>
<TD>
<B>Michael Zucchi</B> <<A HREF="mailto:notzed@ximian.com">notzed@ximian.com</A>><BR>
<I>"born to die, live to work, it's all downhill from here"</I><BR>
<TT>Novell's <A HREF="http://codeblogs.ximian.com/blogs/evolution/">Evolution</A> and <A HREF="http://www.gnu.org/philosophy/free-sw.html">Free Software</A> Developer</TT>
</TD>
</TR>
</TABLE>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>
--=-YfjVIPnl9NaRxzQNVgDv--
--=-piiOgjaBa5B0UnA8dXMc
Content-ID: <1096615358.9716.0.camel@lostzed.mmc.com.au>
Content-Disposition: attachment; filename=zed-48.small.jpg
Content-Type: application/octet-stream; name=zed-48.small.jpg
Content-Transfer-Encoding: base64
/9j/4AAQSkZJRgABAQEASABIAAD/2wBDAA0JCgsKCA0LCgsODg0PEyAVExISEyccHhcgLikxMC4p
LSwzOko+MzZGNywtQFdBRkxOUlNSMj5aYVpQYEpRUk//2wBDAQ4ODhMREyYVFSZPNS01T09PT09P
T09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0//wAARCAAwADADASIA
AhEBAxEB/8QAGQAAAwEBAQAAAAAAAAAAAAAAAwQFAgYB/8QALhAAAgEDAgUEAQIHAAAAAAAAAQID
BBEhABIFEzFBURQigZEGYXE0UmJyobHx/8QAFwEBAQEBAAAAAAAAAAAAAAAABAMCAf/EAB0RAAID
AQEAAwAAAAAAAAAAAAABAgMREjEiMkH/2gAMAwEAAhEDEQA/AK8sEEq35nLaP3e1cW/m8kfdtAfh
824L7I1YFrnaRt8+L40U1ECxiGjLzSCocRYuQhubW7jIxrcFZRzU7q3sh3e8deWvX67/AKX0Xegi
TixevoZdxjhnkk2xBj2Z7DIA74Gs+kgpoaamPLllqE5yPuO4i1+nix7+NS3qatikPNZa+idmjLGx
YE+7r16DHgnTEtRWTVIraiknUrE42mJvYTY/IyfjT66YZjNzkzSSRTrEYTuz0tbpg6oV1V62op5G
3QhV9yn+7t8DXPDiZlaepq0AYIBGEFtuRc2/WwH7aroXho98jNG5RVa4wDYNbzqNsefqdcnmM0J0
pp1kKyRywsdpU46EX/19aT4ioWgmanATG0Mpvcd89750arjMg2L1DfQtnSixTMW5hO0ZBZsEg5t5
xodU+8fhit7jZz4ChQWS99U1lC0H8RNZx74xK2DkAG48ePOtU0UUsQLC6kki/wC+jqtMpeLapjYg
XJyNLcxyr1EUHaWaEspHXPbXVcNkUcCUOjvNv2kAdAehOkVo4LrDEFG9hcnPe+rlUsNNSenUIWkk
ZHfbflqFC475IvqdnyWaRsgl6MNwysp13y8uLG3cTk6LBwCmliFR6lw7XBKdMdj50t+X8RkWOnhV
rbnLfX/dUPx1ivAoTJnmFm+CdIVEIx6XpFQSZxVVH6KrkRRaAudn9I8HXhniSPcyC/ntqzxOjMNS
6uNyMbqT0I1Ogoad6pF5S23C4t1zqOa8Y7xbEDSxmesguHDId4DKQDjGqMqHmNLGygFnujAZF8DF
820/xYpQ8RWcRLtkBINuh6Ef5B0tNRH0L7UEjGzCVTZirDBGfJ+NasrcMf4CnLp6f//Z
--=-piiOgjaBa5B0UnA8dXMc--