KTextEditor

David Faure david at mandrakesoft.com
Tue Oct 8 20:38:50 BST 2002


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 08 October 2002 05:16, Zack Rusin wrote:
> On Monday 07 October 2002 17:19, Christoph Cullmann wrote:
> > Therefor my final thoughts:
> > Use KTextEditor, add your wanted interfaces to it after 3.1 and be
> > happy. Let the user decide if he really wants richtext editing or
> > not. 
> 
> Great, that's exactly what I wanted to hear. I never said KTextEditor 
> would be unsuited for what we do, I was just afraid that people might 
> object extending it so that it provides the functionality we need.
> David, would be so kind to answer my questions about KoText in the 
> process of creating a KoText derived KTextEditor component? And if so 
> should I send them to you or to koffice-devel ml?

Yes, no problem, and koffice-devel would indeed be the right place for this....
but I thought the koffice requirement meant that this solution wasn't acceptable?

- -- 
David FAURE, david at mandrakesoft.com, faure at kde.org
http://people.mandrakesoft.com/~david/
Contributing to: http://www.konqueror.org/, http://www.koffice.org/
Get the latest KOffice - http://download.kde.org/stable/koffice-1.2/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9ozRK72KcVAmwbhARAknIAKCT3lVARxTtXeFX7sWuGqZgEa+VmgCgs9T8
d9F48K2G+4O97OPS635BQZE=
=xsbn
-----END PGP SIGNATURE-----





More information about the kde-core-devel mailing list