Features?

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

Features?
by Evan "JabberWokky" E. on Wednesday 06/Oct/2004, @09:19

In the past week, I've made over two dozen documents, half of them fliers stuffed with complicated graphics, the other half letters and press releases, with KWord.

I don't think I've used anything else in a couple years. But I've also not seen much improvement. Minor bugs that need work arounds (the worst being that overlapping graphics print in "last inserted lays on top" order) are slowly getting fixed.

Of course, it pretty much does everything I need. A bit of improvement in the frames menu and layout would be nice, but I can get it to do everything I need.

Where am I going with this? I'm wondering if anybody has used/read about Scribe and knows what advantages it will bring and if it will alter how KWord works. What changes will this shift in text engine bring?

Related Links

·   Articles on Interviews
·   Also by Evan "JabberWokky" E.
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Features?
by David Faure on Wednesday 06/Oct/2004, @14:21

The discussion/decision hasn't happened yet, but here's what I have in my notes:

If we porting kotext/kword/kpresenter to Qt4's text engine, we gain:
Smaller amount of memory needed per paragraph.
Faster layouting (Lars says the current timer-based layouting won't be needed anymore)
Easier undo/redo support (but this works already, so...)
Brand new, stable, table support?
Support for floating images [does OO have that?] (to be extended to the inline-as-char feature we have now)
Future debugging is done by TT :)
To check:
Repaint only the changed paragraphs. Better: only the changed lines.
WYSIWYG?
Everything-in-one-text design, closer to the OASIS design; but might lead to trouble with frames.

If not, we need to work on
- kerning and better WYSIWYG implementation
- maybe using new QTextFormat (and forking collection class?) for paragraphs etc.
- tables
- anchoring

I'll update that list once I look closer at TP2, this mostly comes from TP1.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"I think I might be the only developer who does not use XEmacs." -- Jono Bacon
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.