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

List:       koffice-devel
Subject:    Re: KWord status
From:       Reginald Stadlbauer <reggie () trolltech ! com>
Date:       2001-02-09 14:11:21
[Download RAW message or body]

On Friday 09 February 2001 13:19, David Faure wrote:
> On Friday 09 February 2001 13:20, Reginald Stadlbauer wrote:
> > On Friday 09 February 2001 13:17, Reginald Stadlbauer wrote:
> > > On Friday 09 February 2001 11:04, David Faure wrote:
> > > > On Friday 09 February 2001 08:27, Thomas Zander wrote:
> > > > > [...]
> > > > > This then boils down to the problem that we need QT3 to use the
> > > > > RichText engine. And since KDE does not compile with the (still
> > > > > alpha) QT3....
> > > > >
> > > > > So we are at a point of being unable to continue until the whole of
> > > > > KDE/koffice can be compiled with QT3.
> > > > > The alternative is to backport the classes, but this has to be done
> > > > > a number of times until we reach a release of QT3/KDE.. (Which I am
> > > > > not going to invest time in ;)
> > > >
> > > > Hmm, and I was starting with another alternative... Rebuilding KWord
> > > > around the current QTextEdit (and accepting its limitations for now
> > > > :), so that when Qt 3 is out, only the final integration needs to be
> > > > done. This is assuming that the QTextEdit doesn't change too much
> > > > between the one we have and the final one - I'm not sure this
> > > > assumption stands, though.
> > >
> > > If you refer with QTextEdit to QTextEdit and not the richtext engine in
> > > general, yes this is right.
> >
> > Oops, which is "the one we have"?
>
> I was talking about the one in the branch.
>
> I definitely agree that QTextEdit (and its engine, everything) are the way
> to go. The question is, what can we do NOW, since we have an old QTextEdit
> around, and the new one requires to wait for Qt 3.

That is a good question. Taking the QTextEdit (or rather QTextView, QTextEdit 
is only a subclass which makes it not to be read only) from the branch and 
starting working on that is probably bad, as the one in the 3.0 snapshots is 
more advanced (has undo/redo with formatting information, zooming, etc.) and 
stable. 

Did anybody try yet to port qrichtext, qtextview and qtextedit back to 2.2? 
It should only require some changes in qrichtext (alignment flags, using 
fm.width( str[ i ] ) instead of fm.charWidth( str, i ) and very few more).



-- 
Reggie (reggie@trolltech.com)
_______________________________________________
Koffice-devel mailing list
Koffice-devel@master.kde.org
http://master.kde.org/mailman/listinfo/koffice-devel

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