Fwd: Bookmarks and intergrated debugger

[Sandy Meier]

What do you think? 

Sandy

----------  Weitergeleitete Nachricht  ----------
Subject: Bookmarks and intergrated debugger
Date: Sat, 28 Aug 1999 19:40:24 +1200
From: jbb <jbb at ihug.co.nz>


Hi Sandy,

I've been looking at bookmarks.

There's a few problems here, in fact they're not very useful in the IDE because
they are only applying to a single file, internally. They look a bit like a
leftover from the kwrite implementation :)

So if you set a bookmark on line 20 in a.cpp then load b.cpp and go to the
bookmark you'll end up at line 20 in b.cpp. Not really what you what.

Although I see that there is a separation between headers and cpps. But that
leads to another problem 

if you set bookmark at line 20 in file a.cpp, go to header a.h then go to the
bookmark nothing (appears to) happen. In actually fact you've just gone to line
20 in the current cpp file, but it doesn't get displayed. It should switch to
the cpp file at least even if it's only the current cpp file and not the
bookmarked one!

However, it does switch correctly to the browser window which is odd.

And there's one actual bug (perhaps...)

Clear bookmarks only clears the bookmarks from the currently displayed type.
Perhaps this is intentional? It seems wrong to me.

Part 2

I've also been looking at adding a debugger into the IDE.

I've have a working system (with bugs and missing features) that allows me to
debug the debugger code I'm writing and the crazy test program to exercise it.

I'd say it's about 80% complete so there's only another 80% to go :-)

(I was working on adding the breakpoints to the lines in kwrite which is why I
was looking at bookmarks). 

I hope you'll be interest in this project for kdevelop, but you may have other
plans when you switch to qt2? If you're not interested in my current code
then I'd like to be involved in any effort to get a debugger intergrated into
kdevelop. Believe me, the compile-debug-fix-compile etc cycle is soooo much
faster with an intergrated debugger that works with the features in kdevelop.

ps
I've also have watch breakpoints (great things), catch breakpoints, exit
breakpoints. (The last two implemented but you cannot get to them from the IDE
yet!) And there's memory dumps, dissassemble code, casting data. modifying
values and more features that won't be too hard to implement once the base is
there. But I still have a way to go yet.
If I could get some help here it'll go alot faster, of course.

-- 
Regards,

jbb