On Jun 6, 2006, at 12:44 PM, Paul McNett wrote:
Write a tool to convert a cdxml class into a .py file (generated Python code).
dabo.lib.DesignerXmlConverter.py does just that. The dump of that conversion is the CLASSTEXT.py debugging detritus that is currently left behind.
Comments on this idea?
For a one-time tool, this would work. But how many times has your initial UI design remained etched in stone? Once you do this conversion, you're stuck with making all future changes in code.
I think that this is something that we should not be focusing on. The spirit of open source development says that if someone finds this important, they should take it upon themselves to invest the time. I want to focus on developing tools for the vast majority of developers, instead of getting sidetracked into individual preferences. How many VFP, VB, Access, Filemaker, Delphi, etc., developers have you heard complain that they have to edit their UI code in that tool's IDE? Only people coming from a "do it all in code" background would be concerned about such things.
-- Ed Leafe -- http://leafe.com -- http://dabodev.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
