From kmail-devel  Mon May 30 21:00:35 2005
From: Ingo =?utf-8?q?Kl=C3=B6cker?= <kloecker () kde ! org>
Date: Mon, 30 May 2005 21:00:35 +0000
To: kmail-devel
Subject: Re: Serial number-related trouble, again
Message-Id: <200505302300.37945 () erwin ! ingo-kloecker ! de>
X-MARC-Message: https://marc.info/?l=kmail-devel&m=111748685015999
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============2050464396=="

--===============2050464396==
Content-Type: multipart/signed;
  boundary="nextPart1558933.Iz0VDvrqt4";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1558933.Iz0VDvrqt4
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 30 May 2005 03:17, Don Sanders wrote:
> On Saturday 28 May 2005 00:32, Ingo Kl=C3=B6cker wrote:
> > Well, if a message is show in the main window and in the separate
> > window then it's both times the same message. It's just two
> > different representations of the message (cf. model-view). The
> > serial number connects the views (and all actions which work on
> > messages) with the message in the folder.
> >
> > Of course, this leads to problems if a message which is shown in
> > the separate reader window is deleted by the user. There are two
> > ways KMail could react:
> > a) Automatically close the separate reader window which shows the
> > deleted message.
> > b) Keep everything working as if the message wouldn't have been
> > deleted.
> >
> > ad a) I guess we all agree that this option sucks and thus is not
> > the way to go.
> >
> > ad b) The problem with this is that we will have to make all
> > actions work on serial number _and_ on KMMessage objects. Obviously
> > that does also suck. So currently the only solution I see is as
> > follows: - All actions work exclusively on serial numbers.
> > - Normally all message views reference the same serial
> > number/physical message.
> > - If a message is deleted in one view while it's still referenced
> > in another view (well, actually only if it's still referenced in a
> > separate message window) then we have to put a temporary
> > (complete?)
>
> (complete, yes I concur).
>
> > copy of the message somewhere (in a local folder on
> > disk? just in memory?)
>
> (local folder on disk is best/required I think. We seem to
> need some kind of working folder to put messages in).
>
> > and assign it a new serial number. Or in
> > fact we could simply keep the serial number.
>
> Yes if it's a move we could even keep the serial number.
> Maybe that would keep things quite simple.
>
> > An alternative to putting a temporary copy into some other folder
> > would be to delay the deletion of the message until the message is
> > no longer needed. Obviously this requires reference counting of the
> > serial numbers.
>
> I like the first alternative better.

But it sucks with respect to IMAP. Since you said we'd need the complete=20
message then this means that for each message which is shown in the=20
separate message window the complete messages (including all=20
attachments) would have to be downloaded from the IMAP server even if=20
the user won't need the attachments. I don't think the first=20
alternative is a reasonable solution.

Regards,
Ingo

--nextPart1558933.Iz0VDvrqt4
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCm371GnR+RTDgudgRAqHiAJ4l95pIP+s81dN3R4Y1IEs1HEj/KQCfewvL
itu7djKWqPYiO6FyEDiCGPs=
=B543
-----END PGP SIGNATURE-----

--nextPart1558933.Iz0VDvrqt4--

--===============2050464396==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============2050464396==--