Re: [Evolution-hackers] eplugin branch, startup-wizard
- From: Not Zed <notzed ximian com>
- To: JP Rosevear <jpr novell com>
- Cc: evolution-hackers lists ximian com
- Subject: Re: [Evolution-hackers] eplugin branch, startup-wizard
- Date: Mon, 13 Sep 2004 15:32:30 +0800
On Sun, 2004-09-12 at 22:10 -0400, JP Rosevear wrote:
On Thu, 2004-09-09 at 07:47 +0800, Not Zed wrote:
> On Wed, 2004-09-08 at 12:39 -0400, JP Rosevear wrote:
> > On Wed, 2004-09-08 at 14:18 +0800, Not Zed wrote:
> > >
> > > hi orl,
> > >
> > > I just turned off the startup wizard in the plugin branch/to be 2.1
> > > branch. It wont work with the new mail config editor, and i'm hoping
> > > it will be going away anyway.
> > >
> > > Currently at startup evo just starts, and not until you need an
> > > account (i.e. you hit new mail) does it popup the normal mail-config
> > > druid.
> >
> > The one other spot we rely on the mailer having at least one account
> > that I know of is in the calendar for creating itip meetings (we list
> > the accounts in an option menu for the user to pick the "organizer" of
> > their meeting).
>
> Well that code should need to check you have an account anyway. Even
> with the startup wizard there's nothing to stop the user deleting all
> of their email accounts.
>
> This uses a composer right?
Yes.
> I guess we could put a check in the composer factory.
It also uses it before the composer.
Well I guess it will have to change to use it afterward. Or better, not let it access the composer directly at all.
The ideal solution might be to have a way to trigger account setup for
whoever may need to.
Well i think the ideal solution wouldn't be using gconf as the way to access the data in the first place.
It doesn't provide a rich enough set of features to manage data consistency.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]