Ed Leafe wrote: > On Jan 31, 2008, at 8:13 PM, Paul McNett wrote: > >>> Is there a way to get the ClassDesigner to save the form >>> information as Python >>> code instead of XML? >> Not currently, however that would be really cool to do. We'd need to >> litter the .py files with tags, most likely, to enable 2-way editing. > > > It's not that easy to do. The output of the DesignerXmlConverter.py > utility works, but it's hardly elegant code. The problem is the amount > of possible complexity that needs to be handled; to do that in a > generic way that works with any possible layout is very difficult; it > would be almost impossible to reverse that process back to XML, and > any editing by the developer would certainly defeat that effort. > > Adrian, why do you want to generate Python code? > > -- Ed Leafe
Being able to output code instead of xml would be a very big plus. And it really doesn't matter it this doesn't work 100 % as the most people seem to prefer writing code. They would use the ClassDesigner as a handy tool for generating code pieces to use in their code. I often tried using the ClassDesigner, but as long as there isn't a way to reuse the output for a long time without risking to lose the work you have done, ClassDesigner is quite useless for me. Don't get me wrong. You have done a impressive tool for the visual design, but the current generated output isn't something i would use as a base for future development. I'm sure other people might think differently, but: Real programmers write code! ;-) Uwe _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
