This looks incredibly awesome. One note: You can only debug Java mode applications, but not Android or Javascript. I realize that this would require three separate XQModes, but perhaps something different is needed... I see that a lot of work went into this, and is going to really help a lot of Processing developers with incredibly basic problems (such as semicolons, array declarations, parentheses...). This changes a lot. Great work!

Thanks calsign for the thumbs up!

I switched to XQMode and I will beta-test it from now. This is a very important step for Processing.

Thank you so much for your work!

cool, if processing 2.0 was a bit more stable by me i would have tried it.

Thank you Manindra
I try to use Processing without any knowledge in programing, and your XQMode is a fantastic help for beginners, saving hours to find an error.

I noticed that when you switch from Java to XQMode some words lose their colour. For example the words: frameCount, mouseX, mouseY, keyPressed, Key, KeyCode, width, turn from blue (#006699) to grey (#7e7e7e), strangely, heigth, turn from blue to black...
Other question: when you switch from java to XQmode, and if you have done changes in your code, you have the message: "Please save the sketch before changing the mode". Is it possible to disable this step, and to switch (from java to XQMode or from SQMOde to Java) without saving the sketch.
Anyway thanks for your useful add to Processing.