Wow, I haven't tried it yet, but it looks good! A fantastic tool that will ease the life of lot of people. Thanks for your work.

I am starting to try it.

First remark, the debug mode doesn't use the theme.txt settings. I have tweaked the colors there, and I get another color scheme in the syntax highlighting. It is annoying as I find the text in the console to be hardly readable on my setup.

Next remarks:
- Setting a breakpoint marks the butter as changed (§ after the tab name). Why?
- I was surprised not to see a Step Into button. I see it is there in the Debug menu, and it has a keyboard shortcut, so that's OK: when debugging, I much prefer using keyboard. Although the choice of keys is unusual. I hope we can customize them (eg. to set them like those in Eclipse).
- Ctrl+J do the Step operation, but it also inserts a line before the current line. It looks like the default keyboard shortcut from the editor is still there.
- Idem for Ctrl+Shift+J...

I report some relatively minor glitches, I find the work you made amazing.
Keep up the good work.

hey, thanks for your feedback!

Ah, I see, you save the breakpoints as  //<>// after the line. Why not.
Shift+button is an OK shortcut for me, even more as I rarely use these buttons (I use keyboard a lot).
" there aren't many unassigned keys left"
F5 to F8 don't seem to do much visible things in 2.0b1...
In Eclipse, F5 is step into, F6 is step over, F7 is step out and F8 is resume.
Handy as it is easy to type and close to each other. But if other people are used to other shortcuts, making them customizable would be great.
Another useful key is Ctrl+R: run until. It should be easy to do: put a temporary breakpoint, resume the run, and when hitting the breakpoint, remove it. Useful to skip a loop, for example.

Great !! This will encourage me to switch to 2.0 :)

Thanks, I always missed a debug-mode in Processing - this will be very useful!
The theme.txt seems to be working now, too.
However, I'm using a dark background with a light grey font, and when I set a breakpoint the line gets highlighted in exactly that color (making the text invisible).
Maybe you could add a new entry in the mode's theme.txt for changing the breakpoint-color?

Edit: Oh, I see now that's already in your todo list.

As a vanilla IDE purist I really thank you for this.

@Eelfroth: thx, for your feedback! I've added some entries to theme.txt so now you should be able to fully customize all debugger-related colors. It's in the latest build:  v0.7.1394

hey I had done a custom syntax highlight a little bit ago, but its super hacky. How hard is it to load a mode? Would be nice if I didn't have to edit core files. Tried to follow what some of your file is doing but no luck, assuming some stuff is loaded into jar files.

This looks great! I'm having trouble getting it to work in 2.0b5.

hey akiersky,

Debug Mode can be run on Processing 2.0b5 after copying ecj.jar located in <processing-root>/modes/java/mode to <sketchbook folder>/modes/DebugMode/mode.

I've uploaded version 0.7.1 of DebugMode just now, it's on the project site: