[Fwd: kdevelop.cpp]

[John Birch]

On Tue, 27 Jun 2000, you wrote:
> On Tue, 27 Jun 2000, John Birch wrote:
> > On Tue, 27 Jun 2000, you wrote:
> > > On Tue, 27 Jun 2000, Falk Brettschneider wrote:
> > > > general. As I said before if one wants to change from dockwidgets to
> > > > another GUI design, he/she have to change all involved parts, in the
> > > > worst case, basically.
> > >
> > > No. The parts are only creating a widget with a parent given as
> > > argument to the create() method of the factory. They don't know
> > > anything about window management or dock widgets. They don't even know
> > > that a class KDevelop exists!
> > >
> > > Bernd.
> >
> > What about parts that have multiple widgets? What would the code look
> > like for that?
>
> Then you should use an interface derived from KParts::Part and provide the
> methods for accessing the multiple widgets/views in that interface. Well,
> you have KDevComponent, no? :-)

This is in relation to parts not knowing how to create and manipulate 
dockwidgets. Currently the idea is a dockwidget wrapper object is created by 
class KDevelop and used to "wrap" the widget created by the part.

But what happens if the part wants more than one dockwidget?

Or do I misunderstand you completely :-)

jbb