Qt->glib main event loop patch (common main loop)
nicolasg at snafu.de
Sat Nov 12 13:19:03 GMT 2005
On Saturday 12 November 2005 12:37, Kevin Krammer wrote:
> On Saturday 12 November 2005 10:51, Nicolas Goutte wrote:
> > On Friday 11 November 2005 20:47, Kevin Krammer wrote:
> > > On Friday 11 November 2005 20:17, Leo Savernik wrote:
> > > > Am Freitag, 11. November 2005 13:57 schrieb nf2:
> > > > > That's because QEventloop code is not cross-platform and not free
> > > > > of GUI related code (at least in Qt3). in fact the ./configure
> > > > > decides, which source-files are used for QEventloop. Secondly, the
> > > > > "common main loop" is only required for the "free desktop"
> > > > > (unix/x11).
> > > >
> > > > Qt3 is past. Qt4 is the future. While developing new features against
> > > > Qt3 may be nice for a case study, you shouldn't make any assumptions
> > > > before you haven't gathered information with Qt4.
> > >
> > > Unless it's one of those local space-time distortions again, it is
> > > likely that most KDE users will not have the benefit of using a Qt4
> > > based KDE for about a year.
> > > Which means any progress in Qt3 integration is still an advantage and
> > > should not be turned down by us lucky few.
> > Just the problem is that any "improvement" of Qt3 will not fit into KDE3,
> > as there will not be any further development version of KDE3.
> There will be no new features in KDE3, true. But this doesn't mean that
> distributors can't ship an extended Qt3 or adapter libraries enabling Gtk+
> applications to to use KDE3's already implemented features.
> Or to write KDE3 compatible plugins using those improvements.
So you suppose that KDE would not need any modification, dont't you?
More information about the kde-core-devel