@cong ling, debugging could be slow in ZeroBrane Studio as it relies on Lua debug hook and does its own processing in it. I’m working on several performance improvements, but can’t say how much faster it’s going to be until they are completed; the results are also highly application dependent.
One of the options to improve performance is to use on()/off() calls to turn debugging on and off. When you turn it off, your application will run with the “original” speed. You can wrap a section of your code into on() and off() calls and then breakpoints and all other debugging functions will work in that section. You can find an example in the section on Selective Debugging here (http://notebook.kulchenko.com/zerobrane/marmalade-quick-debugging-with-zerobrane-studio). I also have demos and descriptions of debugging functions posted here (http://studio.zerobrane.com/documentation.html#Debugging).
I’ve changed some src code of zerobrane to support remote debugging of cocos-2dx and also tips for code.
Have you made your changes available somewhere? Maybe I can integrated them into the main package.
But the tips is very week and IDE don’t support reference jumping.
Can you elaborate on being “week”? Right now auto-complete is using syntax analysis (which is definitely limited), but there are some improvements coming, which will allow to specify methods and returned value types. Reference jumping is being worked on, but probably won’t make it into the next version. Paul.