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.
> 
>     But I'm certain that writing the code in a separate .py file to
> begin with would also be possible. One problem, of course, is how to
> link code in a .py file with the object as represented in the .cdxml
> file. Let's say that I have a button on the third page of a pageframe,
> and I want to write code that adds behavior for when the user clicks on
> it. How would you associate a bit of code in a separate .py file with
> the object that is eventually created from the .cdxml file? There would
> have to be some sort of naming convention, or some other way of the
> framework finding that code and binding it to the correct object when
> instantiated. If you could come up with such a technique, I would
> certainly look into implementing it.
> 
> -- Ed Leafe

Would it be possible to just derive a new class from the
Designer-generated form-class?
The only thing we would need are stubs for all standard-functions.

Uwe

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users

Reply via email to