Hi, folks, I'd like to humbly propose a couple(3, actually) of features which could make Protoeditor much more convenient for debugging:
1) It could be very nice if Protoeditor could highlite/mark somehow global and local variables which were changed since the last debug step. This is very useful for watching which variables got changed.
2) It would be very useful to have an additional Backtrace tab listing all parent function calls which led to the current debug point. And making all these functions source code browsable by clicking the Backtrace list item entry could make it even more useful.
3) How about having Eval/Interactive Shell tab where be possible to execute PHP commands and dump variables?
Sorry, I currently can't contribute to the development, so you can just ignore these requests ;)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The first item is very interesting indeed. There is something similar for the second, which is a combobox with all the backtrace (local tab). Changing the item of the box display the line/file of the call, but maybe there could be some benefit on having this info in it's own tab. For the 3rd, I would have to investigate the support on the debuggers for such thing (I can't remember, for instance, if Xdebug and DBG supports this).
Unfortunately, and being honest here, I'm not sure when I will get back to develop protoeditor. It could be in the end of this year, it could be latter. Right now, I'm setting some priority to bug fixing, but "free time" is becoming a legend for me and diving into protoeditor's code is impractical these days.
Anyway, your requests were heard.
Thiago
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, folks, I'd like to humbly propose a couple(3, actually) of features which could make Protoeditor much more convenient for debugging:
1) It could be very nice if Protoeditor could highlite/mark somehow global and local variables which were changed since the last debug step. This is very useful for watching which variables got changed.
2) It would be very useful to have an additional Backtrace tab listing all parent function calls which led to the current debug point. And making all these functions source code browsable by clicking the Backtrace list item entry could make it even more useful.
3) How about having Eval/Interactive Shell tab where be possible to execute PHP commands and dump variables?
Sorry, I currently can't contribute to the development, so you can just ignore these requests ;)
Hello, and thanks for the requests.
The first item is very interesting indeed. There is something similar for the second, which is a combobox with all the backtrace (local tab). Changing the item of the box display the line/file of the call, but maybe there could be some benefit on having this info in it's own tab. For the 3rd, I would have to investigate the support on the debuggers for such thing (I can't remember, for instance, if Xdebug and DBG supports this).
Unfortunately, and being honest here, I'm not sure when I will get back to develop protoeditor. It could be in the end of this year, it could be latter. Right now, I'm setting some priority to bug fixing, but "free time" is becoming a legend for me and diving into protoeditor's code is impractical these days.
Anyway, your requests were heard.
Thiago