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

List:       kmail-devel
Subject:    Re: [Patch] kmfolderdia
From:       Carsten Burghardt <cb () emedia-consult ! de>
Date:       2001-11-27 17:40:50
[Download RAW message or body]

On Tuesday 27 November 2001 09:20, Michael Häckel wrote:
> On Tuesday 27 November 2001 08:17, Carsten Burghardt wrote:
> > > In general this is nice. It should probably also work correctely, if
> > > already initially an IMAP folder is sectected.
> >
> > The initially selected item is the "Top Level" which is local. If that'll
> > change...ok, I'll put it in.
>
> At least if it is called from the context menu, the current folder is
> selected.
>
> For the case it is called from the main menu I think in most cases the user
> wants to create a top level folder and not for example a subfolder of the
> local inbox if that is selected for example.

In that case the Top Folder is selected and everything's ok.

> > We'll have to set the noContent on these folders that can only contain
> > folders. Then we should grey these out in the normal folder tree to
> > indicate that the user can't put mails in there. I don't see a problem
> > with
>
> I don't think, that grey items in the folder tree look nice. Besides that,
> they are not fully unfuncional. It is possible to select them and to create
> a subfolder or to check for new mails from the context menu.
>
> > The only real problem is to find out whether the server supports mails in
> > subfolders or not. There is no capability command I think. Netscape lets
>
> The UW-IMAP server supports mails in subfolders. It just doesn't supports
> mails in folders, that contain subfolders.

That's what I meant.

> > the user decide but I doubt that all the users know what server their
> > provider has.
> > Perhaps we can test this?
>
> Maybe a solution would be to just create the folder. As soon as the folder
> exists, we can check, if it can contain mails and if it can contain
> subfolders. If any of these two things are not possible, we ask the user,
> what he prefers.

Basically a good idea but pretty complex, you need to create and delete a 
folder and a message to test that.
Then we know the general setting and can apply it to all folders, ok. But what 
to do if folders already have mails and we don't know the setting? Let the 
user create a folder and wait if it fails? That's not very nice.

> > OK, I'll add the expire.
>
> The problem is, that expire is mostly done on exit and that doesn't work
> easily with folders that uses an asyncronous protocol.

Sorry, I meant, I'll add the expire to the disable function.

> Regards,
> Michael Häckel
> _______________________________________________
> kmail Developers mailing list
> kmail@mail.kde.org
> http://mail.kde.org/mailman/listinfo/kmail
-- 
Carsten Burghardt
PGP/GPG: http://www.emedia-consult.de/security.html

_______________________________________________
kmail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail

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