A final word and what to do now (was: A final word (was:Re: What's up and what's hot))
hausmann at kde.org
Fri Aug 10 07:21:19 UTC 2001
On Fri, Aug 10, 2001 at 12:00:23AM +0200, F at lk Brettschneider wrote:
> Ralf Nolden wrote:
> > On Thursday, 9. August 2001 23:38, you wrote:
> > > Technically, QextMDI's tasks are application core functionality and
> > > cannot be moved to a plugin. I learned that during the time when QextMDI
> > > was in the HEAD branch. Note that the whole GUI is handled by QextMDI:
> > > The mainwindow is a QextMdiMainFrm, the tool-views are embedded in
> > > KDockWidgets under control of that single QextMdiMainFrm instance. And
> > > it's clear all docu and source views are QextMdiChildViews. Only if all
> > > those 3 conditions are fulfiled it's possible to switch the 3 MDI
> > > visualization modes.
> > Ok, I'd say that is an option. Two questions:
> > a) how about removing the KDockWidget stuff ? that is buggy as hell and
> > bloats kdeui, now that Qt contains a Dockwidget as well. Could it be made
> > that QextMDI uses that ?
> QDockWidget cannot be docked as tabbed windows. It would mean all
> tool-views cannot be tabbed, TabPage mode would be impossible. :-(
> So I think we're stucked to KDockWidget&Co.
If that's the only reason then we might try to file a bug report :-)
What's the exact problem with tabbing and QDockWidget/QDockArea?
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
More information about the KDevelop-devel