On Jun 5, 2006, at 8:34 PM, Alex Tweedly wrote:

        [sorry, clicked 'Send' too early]

Well, we would love to use Wing, but unfortunately it is proprietary and thus not compatible with integration into Dabo.

You shouldn't need to *integrate* it as a debugger - merely provide a way to get the code somewhere that the debugger can find it, just like any other wxPython app that has its code in Python files.

Well, that's the whole point, isn't it? We *don't* use regular .py files. We don't generate code at all. For Wing to work with .cdxml- created classes, a whole lot of customization would have to be done.

I think the way Wing does it is to have a project file, which is used to store the set of breakpoints (and lots of other things - list of files in the project, cursor position in each file, stat of the windows / GUI, etc.) If you edit the source files within Wing, then it can adjust the breakpoint position accordingly - and if you edit the source files outside Wing, then your breakpoints will "drift".
        
Exactly - it requires a physical .py file - something that we don't use.

Essentially then, all I want <grin> is instead of the classtext.py importing a temp file, it should import a file I specify, and auto- bind any events defined within that to the relevant controls. That should be even easier than my earlier suggestion, because it can be done within the classtext.py

Again, CLASSTEXT.py is debugging output, not anything that is used for anything.

The separation of method code into a separate temp .py file is done each time the class is instantiated. The class is not pulling in the temp .py file; it is spitting it out!

CD has an option setting to say "use external source file" rather than "internal source snippets". When this is enabled, the users must specify (somewhere) the name of the file to be used - and also prevent (or give warning) if the user tried to edit code within CD.

Perhaps this might be something someone will want to tackle further down the road, but right now it doesn't advance us toward our ultimate goals of an IDE that integrates visual design tools, project management, debugging, writing code, etc. If the Class Designer was a finished product, then perhaps, but so much of it is still to be developed. I only added the creation of the temp .py files in order to enable developers to step through their code. That was a major effort to hack that together, and it is one I plan on discarding as soon as possible. I really don't want to create yet another such hack that will be tossed away.

-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com




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

Reply via email to