KSplashScreen (was Re: Qt 3.2 requirement)

Chris Howells howells at kde.org
Fri Jul 25 09:50:34 BST 2003

Hash: SHA1


On Friday 25 July 2003 00:03, Ravikiran Rajagopal wrote:
> FYI: KSplash/ML, which will be included with KDE 3.2 has a managed mode
> which makes it available for *all* DCOP-aware applications, not just for
> KDE startup. It has a plugin architecture (along the lines of window
> decorations) which handles plugins made with C++ code, and is also pixmap
> themeable. Please see the documentation at docs.kde.org which has cut and
> paste code examples.
> I have tried to make it as light as possible (in terms of resources and
> startup time), and will continue to do so as much as possible. It already
> supports global configuration of closing on click, and disabling it
> entirely based on a global config is trivial. If it is started via kdeinit
> (as I expect it will be), I see no reason for it to be any slower than
> QSplashScreen.

I'm not convinced that a something that uses dcop, has a C++ plugin 
architecture and is pixmap themeable is going to be quicker than QSlashScreen 
which is perhaps one of the most trivial classes in Qt, not doing much more 
than use QPainter to draw a pixmap.

I will endeavour to do some testing of performance, but as someone that 
detests splash screens (that's why I wrote KSplashScreen) I think that if 
there are any performance penalties this functionality should be removed from 
KSplash/ML and left to KSplashScreen.

- -- 
Cheers, Chris Howells -- chris at chrishowells.co.uk, howells at kde.org
Web: http://chrishowells.co.uk, PGP ID: 0x33795A2C
KDE/Qt/C++/PHP Developer: http://www.kde.org
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)


More information about the kde-core-devel mailing list