Ed Leafe wrote:
On Jun 3, 2006, at 7:21 PM, Alex Tweedly wrote:
On the other hand, I think CD is a very ambitious project; it
suspect it will be some considerable time before it is fully
developed. The technique of storing the code for handlers in the
cdxml file is interesting - but it means that I can't use the code
editors and debuggers I am used to. I'd much rather use WingIDE for
coding and debugging. It's possible that in the long run CD will
provide a way to do that - but I don't see how, and my guess is that
it may take a while.
FWIW, you can certainly use debuggers with the changes added a
couple of weeks ago. All code is written to a temp .py file, and
replaced with stub calls in the original class. One of the problems
of the original approach, which compiles and execs on the fly, was
that you couldn't step through code. If you add a call to dabo.trace
() in your code, you'll be able to step through its execution.
I guess I'm missing something ....
I have a simple form (one button, one text field). The button has some
code in its "OnHit" handler, and I'd like to put a breakpoint in the
middle of it. The temp .py file doesn't (afaict) contain the code that I
put into the handler, so the line where I want to break at still isn't
anywhere visible.
dabo.trace() seems to run Pdb - which may or may not be a fine debugger,
but I really wanted to use (for example) the WingIDE debugger which I'm
familiar with, and I wanted to insert breakpoints, watched variables,
etc. which (I think) means I need visibility into the code within the
handlers.
--
Alex Tweedly http://www.tweedly.net
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.8.1/355 - Release Date: 02/06/2006
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
