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

List:       kmail-devel
Subject:    Re: Komposer and HTML editing
From:       Don Sanders <sanders () kde ! org>
Date:       2003-12-22 4:33:08
[Download RAW message or body]

On Thursday 18 December 2003 09:04, Ingo Klöcker wrote:
> On Wednesday 17 December 2003 22:23, JES wrote:
> > I'd like to continue adding html editing support for kmail.

Great. What's the status, is the creation of an html message (multi 
part/alternative?) complete? What about the spell checking issues, do 
they still exist? Those were the main issues I recall existing in the 
initial version of the patch I created.

> > It 
> > seems that Zack Rusin made some documentation on Komposer. Where
> > can I find it ?
>
> You can find Komposer here: kdepim/libkdepim/komposer. I don't know
> whether there's also some kind of documentation. You should
> definitely coordinate your work with Zack. KMComposer (at least the
> frontend) is basically dead and will be replaced by Komposer
> shortly after KDE 3.2 (at least that's what I think we intend to
> do). So continuing with adding HTML editing support to KMComposer
> doesn't make any sense. Don, correct me if I'm wrong.

Personally I think it's okay, possibly preferable to make HTML editing 
work with KMComposer.

If there is a working HTML editing patch with no known bugs then I 
don't see any advantage to waiting for the Komposer framework to be 
complete before committing the HTML editing patch.

The advantage of completing HTML editing before the Komposer framework 
is put in place is that the Komposer framework requires an interface 
to be defined for editor classes and it would be preferable for this 
interface to include the methods required for HTML editing from the 
beginning (as opposed to being included as an after thought).

That is the KMComposer code is going to be reused by the Komposer 
framework (I believe) so it makes sense to have the KMComposer 
application code as complete and bug free as possible before moving 
it into a library (where it can be harder to debug).

So I think it's ok to get the HTML editing patch working with 
KMComposer before working on a port to the Komposer framework.

But if the Komposer framework is ready before the HTML editing patch 
then sure it makes sense to commit the Komposer framework code first.

> > Does it describe how to insert Komposer into kmail ?
>
> I can't tell. But Zack will make KMail use Komposer shortly after
> KDE 3.2.
>
> > Is Komposer going to be part of KDE 3.3 ?
>
> Hopefully it's going to be part of the intermediate release of the
> kdepim module (between KDE 3.2 and 3.3/4.0).

Don.
_______________________________________________
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]