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

List:       kde-commits
Subject:    Re: kdeutils/knotes/qt3stuff
From:       Malte Starostik <malte () kde ! org>
Date:       2001-09-26 9:30:14
[Download RAW message or body]

Am Wednesday 26 September 2001 11:15 schrieb Simon Hausmann:
> On Wed, Sep 26, 2001 at 09:57:07AM +0200, Malte Starostik wrote:
> > Am Wednesday 26 September 2001 09:51 schrieb Simon Hausmann:
> > > On Wed, Sep 26, 2001 at 12:20:05AM +0000, CVS by brade wrote:
> > > > kdeutils/knotes/qt3stuff .cvsignore,1.1,NONE qrichtext_p.h,1.8,NONE
> > > > Author: brade
> > > > Wed Sep 26 00:19:55 UTC 2001
> > > >
> > > > Removed Files:
> > > >          .cvsignore qrichtext_p.h
> > > > Log Message:
> > > > Not needed anymore, #include'ing <private/qrichtext.h> ;)
> > >
> > > I don't think they'll keep binary compatibility for private (not
> > > installed) headers. There's a reason for 'private' ;)
> >
> > I'm still tempted to use it for ksirc again, as the current state is
> > pretty bad... unfortunately I still didn't get a reply on qt-interest as
> > to why so much of QRichText is private API...basically anything fancy in
> > there is private :((((
>
> Can't we do it all in 'html' ? The first port of ksirc to richtext was
> using html exclusively and it wasn't too bad IIRC
Then we lose things like enabling/disabling timestamps for text lines that are 
already there, background colours, not too sure about clickable URLs...plus 
some things I have in mind for the future, like provide a popup menu when 
clicking on a nick in the text to do /whois, /msg etc. to that user. Hmm, 
maybe those things are not so important. I don't know, it's just a shame that 
all the great stuff of QRichText isn't publicly available.
-- 
Malte Starostik
PGP: 1024D/D2F3C787 [C138 2121 FAF3 410A 1C2A  27CD 5431 7745 D2F3 C787]

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