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

List:       kmail-devel
Subject:    Re: [PATCH] Copy Filter Action - review please
From:       Andreas Gungl <a.gungl () gmx ! de>
Date:       2004-11-30 21:10:00
Message-ID: 200411302210.00992 () gungl-dd ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Tuesday30 November 2004 00:12, Ingo Klöcker wrote:
> > Don't you think that it's much easier for a user to handle a "Move
> > into Folder" plus a "Copy into Folder" action?
>
> Neither "move" nor "copy" make sense for fetched messages because both
> actions require a source (from where the message is deleted in the
> "move" case and where the "original" message stays in the "copy" case).
> At least from a semantical POV "File into Folder" makes much more
> sense. OTOH, this terminology is also flawed due to the digital nature
> of email messages. There's no "the message". There are just copies of
> the message (on the POP server, in memory, in folders).
>
> Anyway, regardless of what label we use for the action IMO we only need
> one. A distinction between "move" and "copy" would just confuse the
> user. For example, what happens if the user uses "copy into folder" but
> doesn't use "move into folder". The only logical result would be to put
> a copy into the give folder and another copy into the default inbox
> (for non-IMAP accounts).
>
> > What about the usability argument?
>
> That's exactly why I don't want two actions.

So this turns out to become a philosophical discusion but a technical one...

If you insist that File into Folder behaves more in the sense of a copy 
action, why don't you want to call it that way? I mean, this would make the 
users understand what's happening.

I would be surprised to find copies of a message in several folders after 
using File into Folders to move a message around. How should File into 
Folder "trash" work? I mean, you still have a copy in the folder from which 
you intended to delete the message.

IMHO the delivery problem also isn't a problem. Fetched messages "normally" 
appear in the inbox (or the specified folder). So you have at least a 
virtual source to delete them from after applying File into Folder. That 
you don't store them in the inbox is rather an optimization than a reason 
to complain about a missing source folder in that case. Finally, you delete 
them from the POP server (or you really have a source folder in the IMAP 
case).

That we currently avoid subsequent moves has technical reasons. We could 
certainly work around that and allow moving messages around via a filter 
sequence. What's wrong with that?

Regards,
Andreas

[Attachment #5 (application/pgp-signature)]

_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel


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