Re: [Evolution-hackers] calendar EPlugin plans
- From: Not Zed <notzed ximian com>
- To: JP Rosevear <jpr novell com>
- Cc: David Trowbridge <David Trowbridge Colorado edu>, evolution-hackers lists ximian com
- Subject: Re: [Evolution-hackers] calendar EPlugin plans
- Date: Mon, 18 Oct 2004 10:02:38 +0800
On Fri, 2004-10-15 at 10:36 -0400, JP Rosevear wrote:
On Thu, 2004-10-14 at 02:42 -0600, David Trowbridge wrote:
> On Thu, 2004-10-14 at 09:01 +0800, Not Zed wrote:
> > On Wed, 2004-10-13 at 01:34 -0600, David Trowbridge wrote:
> > > Since I obviously haven't communicated my plans properly to everyone,
> > > here's a short roadmap of what I plan to do.
> > >
> > > 1. EConfig-ize the calendar properties window
> > > - this is mostly done. Pending some cleanup, I should have a patch off
> > > to e-p for review soon.
> > >
> > > 2. EConfig-size the new calendar window
> > > - this is pending UI decision
> > >
> > > 3. Add some API to allow plugins to register new sources and a calendar
> > > component init hook. The goal of this is to allow plugins to detect the
> > > absence of and register new top-level sources, similar to the existing
> > > migration code. This will make it so new calendar backends can be
> > > distributed completely independent of evolution.
> > I don't understand why you need this at all?
> > Doesn't the e-source-list manage all of these? You should just be
> > adding a new source the same way other sources are added, and they'll
> > just 'work', wont they?
> It sounds like what ought to happen is a separation of source type from
> the source groups.
Yes, that is my thought as well.
Strange, I thought that was the entire point of allof the new code in 2.0, i.e. ESource vs ShellFolder or whatever it was.
] [Thread Prev