any plans to port MDI and debugger

[Richard Dale]

I've just checked out the latest KDevelop 3.0 - nice work Bernd! I've reviewed
the debugging part code (nice work too jbb), and I think the best thing to
do is to copy the code into a new 'javadebugger' part. Otherwise, you're trying
to make some quite tricky code more flexible than it was originally intended, at
the same time as adding a new debugger. I would solve one problem at once.
When the jdb frontend is working, perhaps look into consolidating them back
together again.

-- Richard


On Tue, 17 Apr 2001,  Bernd Gehrmann wrote:
> On Tue, 17 Apr 2001, Richard Dale wrote:

> That depends whether it makes sense to make a completely separate part or
> to share as much code as possible with the gdb frontend. If it's just the
> gdbcontroller class that is replaced then you can easily make a new part
> by creating one of the controller classes in DebuggerPart depending on
> some argument given to the constructor - this is how C and C++ are dis-
> tinguished in the CppSupport part. Something like
> 
>   controller = java? (new JdbController(blah blah)) 
>                    : (new GdbController(blah blah));
> 
> But in practice it's probably more complicated because you also need
> a different parser...

-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«