[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: KMail I (1/2)
From:       Stefan Taferner <stefan.taferner () gmx ! at>
Date:       2001-07-25 6:50:03
[Download RAW message or body]

On Tuesday, 24. July 2001 14:06, Don Sanders wrote:
> On Tuesday 24 July 2001 09:17, Stefan Taferner wrote:
[...]
> > The object tree in the KMFolderTree widget would look
> > like this: KMFolderGroupManager
> > +- KMFolderGroupMbox
> >   +- KMFolderMbox
> >   +- KMFolderMbox
> >
> > +- KMFolderGroupImap
> >   +- KMFolderImap
> >   +- KMFolderImap
> >
> > With the assumption that the user has mbox folders for
> > his local folders and one imap account with two remote
> > folders in it.
> >
> > The KMFolderGroupManager is some simple management object
> > that knows about all the groups of folders the user has.
> > It would be possible to have a completely imap-only kmail
> > this way, for example.
>
> Hmm, yes inheritance makes some sense here.
>
> I don't think the KMFolderGroup* classes are needed though
> since any KMFolder* can have child folders.

But you need somebody who owns the connection, e.g. to
the IMAP server. The KMFolderGroupMbox could hold the base
path to the mail folders (~/Mail usually), etc.

This can be of course done without the group objects too, but
IMO having them is a clearer design.

--Stefan
_______________________________________________
Kmail Developers mailing list
Kmail@master.kde.org
http://master.kde.org/mailman/listinfo/kmail

[prev in list] [next in list] [prev in thread] [next in thread]