class KDevelop

Ralf Nolden Ralf.Nolden at
Thu Jun 15 19:52:25 UTC 2000

Falk Brettschneider wrote:
> Hi,
> Ralf Nolden wrote:
> >
> > I´m currently implementing CKDevelop from scratch as KDevelop and then
> > want to put it to CVS when the UI is complete and the normal slots that
> > are called by the UI are in at least as frame functions.
> If you want to rewrite this class, I strongly advise to divide at least
> in _two_ classes! One for the main widget and one for the application
> framework/logic. I did so in our commercial application and it reduced
> the class size a lot, furthermore with a good interface between both
> classes one can replace the main widget (GUI) by keeping the framework.
That´s what I planned in some way ;-)

> > I´ve
> > inherited from KParts::Mainwindow, but I see there will be some
> > complications with the inheritance of DockMainWindow from KTMainWindow,
> > not from KParts::MainWindow. Could you change that...
> What? DockMainWindow shouldn't inherit KTMainWindow but
> KParts::MainWindow? Well, I fear that isn't possible 'cause it breaks
> the whole Dockwidget class set code a know KDE2 is almost
> interface-frozen, and some other programs uses the Dockwidgets as it is.
> Is KParts::MainWindow completely different than KTMainWindow? In that
> case I see big problems...
How about multiple inheritance ? DockMainwindow and KParts::MainWindow
both inherit KTMainWindow so I think it´s worth a try ?

Maintainer's Motto: If we can't fix it, it ain't broke.  

Ralf Nolden

The KDevelop Project

Email: rnolden at

More information about the KDevelop-devel mailing list