The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: QSplashScreen
by Chakie on Thursday 24/Jul/2003, @05:06
|
Well, it means that all apps don't need to roll their own splash implementation, thus reducing bloat.
|
[
Reply To This | View ]
|
Re: QSplashScreen
by fault on Thursday 24/Jul/2003, @08:12
|
The fact that KDE/Qt applications had to roll their own SplashScreen widgets is evidence that TT's customers wanted a SplashScreen widget in Qt..
|
[
Reply To This | View ]
|
Re: QSplashScreen
by David Johnson on Thursday 24/Jul/2003, @11:01
|
It's a trivial implementation. It doesn't cause any bloat. It is essentially a bare widget that displays a pixmap and starts a timer. At most it has 20 lines of real code.
|
[
Reply To This | View ]
|
Re: QSplashScreen
by zeroskill on Monday 28/Jul/2003, @03:51
|
It's better than a timed splash screen. This new splash widget displays automatically until the application is opened. Thus, no timer. It's automatic. Now, instead of a crappy timed splash screen in 20 lines, you can have a fully auto splash screen in 3 lines.
|
[
Reply To This | View ]
|
|
Re: QSplashScreen
by Chris Howells on Friday 25/Jul/2003, @09:16
|
It's the opposite of bloat. Before applications that wanted a splash screen had to write one from scratch. Now applications can use QSplashScreen (or KDE developers the soon to be KSplashScreen) therefore reducing code duplication.
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|