A little review of kdecore & kdeui

Esben Mose Hansen kde at mosehansen.dk
Sat Apr 8 07:47:08 BST 2006

On Saturday 08 April 2006 00:42, David Faure wrote:
> On Thursday 06 April 2006 01:21, Thiago Macieira wrote:
> > In any event, the question of whether we should have a libkdenetwork core
> > library is still a valid one
> BTW, let's not forget that many of those who investigated application
> startup times have said: we should group our libraries, not split them.
> Some even suggested a "libkde" with everything in it. I know that it seems
> messy, I know that Qt is going the split-up route (so we should do at least
> a core/gui separation), but still, we can use subdirs inside the libs code
> (like qt) while still providing only few (bigger) libs rather many smaller
> ones, since it seems to help startup times.
> > >./kapplication.cpp:556:  (void) KClipboardSynchronizer::self();
> >
> > What does that do? Why do we need a clipboard synchroniser? What's
> > missing from QClipboard?
> No idea, better ask Lubos or check the logs.

It is not used since I commit I made a long while ago. Klipper handles the 
clipboard synchronization, if desired.


More information about the kde-core-devel mailing list