feature request - debugger hooks
Posted: Wed Feb 26, 2003 6:06 pm
Hi folks,
I've been using TextPad every working day for the last 7-8 years. It's fantastic. However, I've recently had to start using an IDE for some PHP coding (sniff), because the DBG debugger doesn't have an interface and needs supported IDE.
However, it would seem that it's not too tricky to support it and add new COM classes which tie in with new IDEs.
That got me thinking. We all know that TextPad should remain as generic as possible. How about creating a new menu in TextPad with the Run, Debug, Step Into, Step Over, Step Out, Stop Debugging, Add Watch, Add Breakpoint, Clear Watches, Clear Breakpoints, Profile etc. and a new Clip Library type window which listed the current variables, watches, output etc. Then these would call add on wrappers which in turn could work with DBG, JDBG and other desired debuggers.
The facility would be built in to TextPad, but the API would have to be written seperately. Helios would kick us off with a couple of useful ones (DBG for PHP please ;¬)) and then others could be added as needed. TextPad as a lightweight multi-language IDE ;¬)
Is this unfeasable/missing the point?
I've been using TextPad every working day for the last 7-8 years. It's fantastic. However, I've recently had to start using an IDE for some PHP coding (sniff), because the DBG debugger doesn't have an interface and needs supported IDE.
However, it would seem that it's not too tricky to support it and add new COM classes which tie in with new IDEs.
That got me thinking. We all know that TextPad should remain as generic as possible. How about creating a new menu in TextPad with the Run, Debug, Step Into, Step Over, Step Out, Stop Debugging, Add Watch, Add Breakpoint, Clear Watches, Clear Breakpoints, Profile etc. and a new Clip Library type window which listed the current variables, watches, output etc. Then these would call add on wrappers which in turn could work with DBG, JDBG and other desired debuggers.
The facility would be built in to TextPad, but the API would have to be written seperately. Helios would kick us off with a couple of useful ones (DBG for PHP please ;¬)) and then others could be added as needed. TextPad as a lightweight multi-language IDE ;¬)
Is this unfeasable/missing the point?