=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 30 November 2002 11:53, Christian Gebauer wrote:
> On Friday 29 November 2002 21:10, Ingo Kl=F6cker wrote:
> > In spirit of the continued fusion with kmail we should consider to
> > base this article viewer and the message viewer (KMReaderWin) on
> > the same super class. This would most likely require to start using
> > a common message class which should be based on kmime.
> >
> > So there are basically three tasks:
> > - switch KMMessage and friends from mimelib to KMime (KMail
> > developers) - move all code which can be shared by both apps from
> > KMReaderWin into KReaderWidget (any volunteers?)
>
> I would also like to get some KNode features into the common viewer
> widget, for example:
> * inline attachment display
KMail can display attachments inline as well as as icons.
> * handling of signatures (hiding or showing a
instead of "-- ")
No objections.
> * interpretation *of* /markup/ _tags_
No objections either.
> Roberto, do you think we can handle this together?
>
> > - make use of KReaderWidget in knode (Christian)
> >
> > The problem is that the third task can't be started before at least
> > the second task has been completed. The first task is not crucial
> > for the other two tasks.
>
> Well, without common message classes we would have to use ugly
> wrapper classes on either the kmail or knode side.
Yeah, that's the problem. I currently don't know whether it makes sense=20
to work on the common KReaderWidget without having common message=20
classes since a lot of code in the KReaderWidget involves parsing of=20
the message. Maybe someone else can comment on this.
Regards,
Ingo
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE96PrjGnR+RTDgudgRAlNrAJoD5meLH4B9FT1msi3AV0CvhZC5tQCgiL22
B9CEnLIA4MDmQSdlfYIg0+M=3D
=3D75Ht
=2D----END PGP SIGNATURE-----
_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail