Re: [Evolution-hackers] External editor plugin
On Tue, 2008-09-16 at 17:27 -0300, Marco Túlio Gontijo e Silva wrote: > Hello, > > I wanted to addapt the external editor plugin for evolution to work more > or less as this feature in claws-mail. I think it should be invoked > from the composer, and edit only the body of the mail, no the To: > Subject: etc fields; and to be able to configure it to run automaticaly > when the composer started. I've never wrote a plugin for evolution, and > I started reading the docs, but I haven't found any part talking about > the composer, so I wondered if this is possible. What do you think of > the idea? Will such a workflow be not best done by having vi/emacs style key-bindings for the composer body area , rather than opening a external program ? I have not seen how this is done in claws-mail. Is it external editor embedded into the composer body area ? > > I noticed that [0] and [1] are differents. What version should I use? > > Greetings. > > 0: > http://svn.gnome.org/viewvc/evolution/trunk/doc/devel/evolution-plugin-manual.xml?view=markup > 1: > http://www.gnome.org/projects/evolution/developer-doc/eplugin/index.html > Sadly, both these versions does not have all the hooks covered yet afaik. You can start with (1). We will be updating the plugin doc soon. -- Sankar ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
[Evolution-hackers] External editor plugin
Hello, I wanted to addapt the external editor plugin for evolution to work more or less as this feature in claws-mail. I think it should be invoked from the composer, and edit only the body of the mail, no the To: Subject: etc fields; and to be able to configure it to run automaticaly when the composer started. I've never wrote a plugin for evolution, and I started reading the docs, but I haven't found any part talking about the composer, so I wondered if this is possible. What do you think of the idea? I noticed that [0] and [1] are differents. What version should I use? Greetings. 0: http://svn.gnome.org/viewvc/evolution/trunk/doc/devel/evolution-plugin-manual.xml?view=markup 1: http://www.gnome.org/projects/evolution/developer-doc/eplugin/index.html -- marcot Página: http://marcotmarcot.iaaeee.org/ Blog: http://marcotmarcot.blogspot.com/ Correio: [EMAIL PROTECTED] XMPP: [EMAIL PROTECTED] IRC: [EMAIL PROTECTED] Telefone: 25151920 Celular: 98116720 Endereço: Rua Turfa, 639/701 Prado 30410-370 Belo Horizonte/MG Brasil ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Evolution: Taking forward...
Hello On Mon, 2008-09-15 at 12:35 +0100, Ross Burton wrote: > On Fri, 2008-07-11 at 04:21 -0600, Srinivasa Ragavan wrote: > > It would be really helpful if you can post a public/explicit mail with > > permissions to do it, or code pointers - if you think you wrote a > > piece of Evolution code & object. > I have submitted very tiny bits, sorry, i do not remember which ones :( Permission granted for any code I've produced. > > Ross > ___ > Evolution-hackers mailing list > Evolution-hackers@gnome.org > http://mail.gnome.org/mailman/listinfo/evolution-hackers -- Ritesh Khadgaray Ph: +919970164885 Desktop LinuX N Stuff, RHCE Software Maintenance Engineer, Pune, Red Hat ॐ मणि पद्मे हूँ Eat Right, Exercise, Die Anyway. ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Removing libical fork, moving to new upstream?
Hello! A while ago in this thread I argued in favor of keeping the old functions around with their old semantic to preserve backwards compatibility. I still stand by that logic for *libical* users. But later it occurred to me that for *libecal* users this is an API change because code which was compiled against the latest libecal may free the memory and therefore crash when the libical implementation is no longer the one from libecal, but the upstream version. Therefore the revision will have to be bumped from LIBECAL_CURRENT=9 LIBECAL_REVISION=1 LIBECAL_AGE=2 to LIBECAL_CURRENT=10 LIBECAL_REVISION=0 LIBECAL_AGE=0 SyncEvolution would remain binary compatible *without* a revision change because it checks at runtime how memory handling is to be done. *With* the revision change I'll have to compile another version of it :-/ But there might be other users of the library which don't check at runtime (Evolution itself for example) and therefore it is safer to bump the revision. I'd be more than happy to hear that I'm too concerned here and that the revision change won't be necessary. -- Bye, Patrick Ohly -- [EMAIL PROTECTED] http://www.estamos.de/ ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Removing libical fork, moving to new upstream?
On Tue, 2008-09-16 at 09:37 -0400, IGnatius T Foobar wrote: > > Since we do really want to remove the fork and pick up packages from > > upstream, I can change the apis in evolution related packages if a new > > set of apis with some suffix is provided from libical upstream. > > > Many of you have probably already read this on the libical mailing list, > but just in case: > > I have applied Chenthill's memory management patches (only to the > 'libical' directory and to the examples -- still have to do the > 'libicalcap' and 'libicalss' directories) using function names ending in > "_r". For example, icalcomponent_as_ical_string() is now simply a > wrapper around icalcomponent_as_ical_string_r() which places the new > string buffer on the ring before returning it to the caller. The > functions whose names end in "_r" have had Chenthill's memory management > patches applied to them. > > Do we still need to add the HANDLE_LIBICAL_MEMORY hack to make the old > function names act like the new ones? Chenthill's most recent message > (quoted above) seems to imply that the Evolution team is willing to move > to the new function names. Let me know. IMHO, HANDLE_LIBICAL_MEMORY can be removed. thanks, Chenthill. ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] [Fwd: Re: [Fwd: Evolution: Taking forward...]]
I have been mailed privately about this: Permission granted for any pieces of code I have produced. Djihed On Tue, Sep 16, 2008 at 10:08 AM, Paolo Borelli <[EMAIL PROTECTED]> wrote: > I've been told to send this one also to the mailing list, so here it > goes. > > > Ciao >Paolo > > > -- Forwarded message -- > From: Paolo Borelli <[EMAIL PROTECTED]> > To: Srinivasa Ragavan <[EMAIL PROTECTED]> > Date: Fri, 12 Sep 2008 19:11:27 +0200 > Subject: Re: [Fwd: Evolution: Taking forward...] > On ven, 2008-09-12 at 21:41 +0530, Srinivasa Ragavan wrote: >> Hey Paolo, >> >> As you are aware, we are in the process of re-licensing(See the attached >> mail), we are >> now contacting all the code committers for explicit permission mails. We >> have completed >> contacting almost 85% of the people. You have also committed some amount of >> code for >> Evolution. Can you approve the license change for the code you wrote? >> >> Looking forward for much more contributions from you :-) >> > > I think I only committed *after* you announced the relicensing :-) > > That said, sure, I give permission to relicense any contribution I made. > > Paolo > >> -Srini. >> >> >> Messaggio email attachment, "Forwarded message - Evolution: Taking >> forward..." >> > Forwarded Message >> > From: Srinivasa Ragavan <[EMAIL PROTECTED]> >> > To: [EMAIL PROTECTED], evolution-hackers@gnome.org >> > Subject: Evolution: Taking forward... >> > Date: Fri, 11 Jul 2008 04:21:56 -0600 >> > >> > Hello guys, >> > >> > We have had a set of problems that we are carrying around for some time >> > like : >> > >> > * Copyright assignments, which is not the best way looking for the >> > future of Evolution. It sucks and sort of limits contributions to >> > Evolution and we wanted to drop it. >> > * The current licensing incompatibility issues of Evolution with >> > Samba4/libmapi (GPLv3). Evolution needs to link with libmapi/samba4 for >> > the new mapi based connector being developed for Exchange 2007. >> > >> > So here is the plan : >> > >> > * Drop Evolution copyright assignments and make it really easy to >> > contribute to Evolution >> > * Move Evolution licensing to "LGPL v2 and LGPL v3" to let us >> > re-use the code more easily around the platform. This also moves us >> > closer to Thunderbird's MPL/LGPL model. >> > >> > We think this is good for Evolution and (of course) we continue to invest >> > in Evolution. We are also working to ensure we have the rights to >> > re-license all of the code. We will do the licensing/header changes as we >> > audit the code ownership situation. >> > >> > It would be really helpful if you can post a public/explicit mail with >> > permissions to do it, or code pointers - if you think you wrote a piece of >> > Evolution code & object. >> > >> > We are really excited about this and we feel this would really help >> > Evolution a lot. We need your support now for making this change and to >> > take Evolution to great heights. >> > >> > Thanks for your contributions and support. >> > >> > -Srini. >> > ___ >> > desktop-devel-list mailing list >> > [EMAIL PROTECTED] >> > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > > ___ > Evolution-hackers mailing list > Evolution-hackers@gnome.org > http://mail.gnome.org/mailman/listinfo/evolution-hackers > > ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
[Evolution-hackers] [Fwd: Re: [Fwd: Evolution: Taking forward...]]
I've been told to send this one also to the mailing list, so here it goes. Ciao Paolo --- Begin Message --- On ven, 2008-09-12 at 21:41 +0530, Srinivasa Ragavan wrote: > Hey Paolo, > > As you are aware, we are in the process of re-licensing(See the attached > mail), we are > now contacting all the code committers for explicit permission mails. We have > completed > contacting almost 85% of the people. You have also committed some amount of > code for > Evolution. Can you approve the license change for the code you wrote? > > Looking forward for much more contributions from you :-) > I think I only committed *after* you announced the relicensing :-) That said, sure, I give permission to relicense any contribution I made. Paolo > -Srini. > > > Messaggio email attachment, "Forwarded message - Evolution: Taking > forward..." > > Forwarded Message > > From: Srinivasa Ragavan <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED], evolution-hackers@gnome.org > > Subject: Evolution: Taking forward... > > Date: Fri, 11 Jul 2008 04:21:56 -0600 > > > > Hello guys, > > > > We have had a set of problems that we are carrying around for some time > > like : > > > > * Copyright assignments, which is not the best way looking for the > > future of Evolution. It sucks and sort of limits contributions to Evolution > > and we wanted to drop it. > > * The current licensing incompatibility issues of Evolution with > > Samba4/libmapi (GPLv3). Evolution needs to link with libmapi/samba4 for the > > new mapi based connector being developed for Exchange 2007. > > > > So here is the plan : > > > > * Drop Evolution copyright assignments and make it really easy to > > contribute to Evolution > > * Move Evolution licensing to "LGPL v2 and LGPL v3" to let us re-use > > the code more easily around the platform. This also moves us closer to > > Thunderbird's MPL/LGPL model. > > > > We think this is good for Evolution and (of course) we continue to invest > > in Evolution. We are also working to ensure we have the rights to > > re-license all of the code. We will do the licensing/header changes as we > > audit the code ownership situation. > > > > It would be really helpful if you can post a public/explicit mail with > > permissions to do it, or code pointers - if you think you wrote a piece of > > Evolution code & object. > > > > We are really excited about this and we feel this would really help > > Evolution a lot. We need your support now for making this change and to > > take Evolution to great heights. > > > > Thanks for your contributions and support. > > > > -Srini. > > ___ > > desktop-devel-list mailing list > > [EMAIL PROTECTED] > > http://mail.gnome.org/mailman/listinfo/desktop-devel-list --- End Message --- ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Evolution: Taking forward...
Hi, [As Srini asked me to do this,] I approve the planned license change for all of the code I ever contributed to Evolution. Cheers, -Michael ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
