Re: [Evolution-hackers] creating new calendars, contact groups, and task groups
- From: Rodrigo Moya <rodrigo ximian com>
- To: Chris Toshok <toshok ximian com>
- Cc: Larry Ewing <lewing ximian com>, Anna M Dirks <anna ximian com>, evolution-hackers ximian com
- Subject: Re: [Evolution-hackers] creating new calendars, contact groups, and task groups
- Date: Tue, 06 Apr 2004 10:39:23 +0200
On Mon, 2004-04-05 at 17:13 -0700, Chris Toshok wrote:
> On Mon, 2004-04-05 at 06:26 -0500, Larry Ewing wrote:
> > On Tue, 2004-03-30 at 16:51 -0500, Anna M Dirks wrote:
> > > Greetings all.
> > >
> > > The purpose of this mail is to solicit feedback from you about a
> > > possible redesign of the tools used to add new groups of contacts, new
> > > groups of tasks, and new calendar in Evolution 2.0.
> > >
> > > Currently, all of these things are configured using wizards. This
> > > approach is inappropriate, because in most cases there is very little
> > > information required to add a new group -- so that adding one using a
> > > wizard takes significantly more time (and mouse clicks) than is
> > > necessary.
> > >
> > > I propose that replace these wizards with a set of simple dialogs.
> >
> > As I sat down to implement this I noticed this change may end up causing
> > us problems in the future. With the druid based approach if a new
> > evolution-data-server backend is added then we'd simply need to add the
> > new source type to the type selector on the first druid page and replace
> > the subsequent druid pages with controls the backend provided. With the
> > new plan of simple dialogs I don't see how we could add new types in the
> > future if the options they need don't match the options of the current
> > sources exactly.
>
> hm, right - unless we dynamically add pages to the dialog depending on
> the source type, which is kind of a gross idea.
>
> we have a bounty for a contact db backend. what sort of information
> would we need for that? db server hostname, port, database name, user
> password? Assuming of course the schemas are hardcoded.
>
if the DB backend uses libgda, it will just need the name of the GDA
data source, and probably a button to allow the user to create it
(calling gnome-database-properties) if it's not created yet.
cheers
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]