[Fwd: kdevelop.cpp]

John Birch jbb at kdevelop.de
Tue Jun 27 09:07:44 UTC 2000

On Tue, 27 Jun 2000, you wrote:
> Hi!
> John Birch wrote:
> > So, are we arguing a philosophical viewpoint, rather than a technical
> > implementation problem ?
> Yep. The technical problems are depending on those things.
> > Doesn't the centralised approach mean that every window must be "created"
> > by kdevelop - that doesn't feel right to me.
> It means the inner view widgets (ClassView, BreakPointManager,...) are
> created by every part itself. But they are docked together centralized, no
> part does not know nothing about docking, that's why dockwidgets are
> created centralized (class KDevelop), not in the parts.

You're saying that there are x number of "outer parts" that wrap the inner 

In the debuggers case we have disassembler, var, breakpoint, framestack inner 
widgets. Each must have a dock outer widget that must be created by kdevelop.

How is this done?

What happens if I create a perl debugger part that has only var, breakpoint, 
and framestack?

> > Hmm, what to do. We could do with a whiteboard, a few cold beers, and a
> > summer's afternoon, in the same room :-)
> Summer is here. Or we must wait until December. The beer is always cold in
> Germany ;-)

More information about the KDevelop-devel mailing list