Yes, the command window is great. When developing wxPython applications I us pywrap a lot (and I always have a pycrust window open to test things, see calltips etc. PyDev's intellisense isn't working very well. I hope Wing IDE is a little better here.) I haven't used wxPython directly since I found dabo. I have only created small database-centric applications 'til now, so I'm looking forward to my next projects.
-Simn -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Leafe Sent: 30. juni 2006 16:18 To: Dabo Users list Subject: Re: [dabo-users] Developing and debugging dabo applications On Jun 30, 2006, at 9:53 AM, Simen Haugen wrote: > Ok, I see that you both use print statements as a debugging tool. I also do a LOT of debugging from the Command Window (the dShell, based on PyCrust), which is why I added it to the base menu. In any Dabo app, I can press Cmd-D/ Ctrl-D and have an interactive session where I can inspect objects, change their properties, call their methods, etc. Being able to work with live objects is critical when dealing with GUI issues. For example, when I refactored out the image code from all the classes that display images, I would run the class to bring up the test form for that object, and then address the control directly to manipulate it and make sure that each change of a property did what it's supposed to do, such as refresh at the right time, size the image appropriately, change the text if applicable, etc. -- Ed Leafe -- http://leafe.com -- http://dabodev.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
