KSplashScreen (was Re: Qt 3.2 requirement)

[Carsten Pfeiffer]

-----BEGIN PGP SIGNED MESSAGE-----

On Friday 25 July 2003 01: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.

So this will essentially become a splashscreen server? This sounds quite a bit 
like overkill to me and I doubt that coding a splashscreen with C++ plugins 
and DCOP is easier to do than using a simple K/QSplshScreen class.

Cheers
Carsten Pfeiffer
-----BEGIN PGP SIGNATURE-----

iQEVAwUBPyETiqWgYMJuwmZtAQG4SAf+Mojp6yX1A33F5qwyFndA85OaZvRm76fO
ZCwjXcyTn8XJVgokC0MSzvkURjxKEV7Hmr9Yq5olrwYPWIoxOvpaQHVKyr3Fl+us
IVtXbVfiRrnw4qEm+TruS6GDPHIwBWiAjJ1DvpeKOZ6Dj6C1BzKJZcLOKBIhJ7vb
wfInA838LgdE/7aV0kPSeCLjYCEcM5YTHqiUWelv1gjrlgYEmRBSU10pfAz6xbDZ
al97mKbunnFnhEHsfVBi9Ke4yQtQkFHCBIHYtCXGdv8kv3CZpEpIkCxm4YiYpsx/
6MIWSAdirNukxo6CQ+I2dxZg0wN+kapjXUdahlE9yUj4c6JUTOLJpA==
=S/hJ
-----END PGP SIGNATURE-----