Re: [evolution-patches] New implementation of EMsgPort
- From: Philip Van Hoof <spam pvanhoof be>
- To: Matthew Barnes <mbarnes redhat com>
- Cc: evolution-patches gnome org
- Subject: Re: [evolution-patches] New implementation of EMsgPort
- Date: Tue, 17 Oct 2006 14:05:18 +0200
On Tue, 2006-10-17 at 07:59 -0400, Matthew Barnes wrote:
> Sounds good. Speaking of which, see also:
Excellent
> Kill EMutex (with patches):
> http://bugzilla.gnome.org/show_bug.cgi?id=356177
Patching mine
> Kill EThread (with patches):
> http://bugzilla.gnome.org/show_bug.cgi?id=362638
Compiling mine
> Kill CamelException (no patches yet):
> http://bugzilla.gnome.org/show_bug.cgi?id=354075
Checking out :)
> I'd be very interested in seeing Camel become GObject-based. Let me
> know if there's anything I can do to help.
I was hoping a little bit on seeing libspruce and GMime mature a little
bit for that.
But I had this funny idea of simply refactoring CamelObject to let it
inherit from GObject and re-implement the CamelObject functionality
using GObject tools.
Might be a naive idea. I don't know. It would be nice to see CamelObject
enjoy the same features and enhancements GObject enjoys today. Like for
example the gslice allocator and GTypeInterface.
At this moment that's only a nice to have, for tinymail. So it's not on
a high priority list of myself. But maybe we can, indeed, take a look at
it.
--
Philip Van Hoof, software developer
home: me at pvanhoof dot be
gnome: pvanhoof at gnome dot org
work: vanhoof at x-tend dot be
blog: http://pvanhoof.be/blog
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]