On Jan 12, 2006, at 11:14 AM, Don Taylor wrote:
However, a question. Looking at:def main(): app = dabo.dApp() app.MainFormClass = "test2.cdxml" app.start()I am guessing that dApp processes the test2.cdxml file to generate temporary Python containing a whack of wxPython stuff. If so then can I look at this generated Python somehow?
No, there is no generated code at all. Look at the source for dabo.ui.uiwx.dFormMixin.py. The 'src' parameter will be the path defined in the MainFormClass property. The dFormMixin __init__ process recognizes that as a Class Designer file, and proceeds to extract the code and child object definitions from it. It then compiles the code and re-creates the child objects.
I also noticed that the Editing window has a (non-operational) Save as Class menu item - is this going to be used to save a Python/ wxPython version of the form?
No. What I have in mind for that is the ability to create a reusable UI component that can then be dropped on another form. Right now you're limited to only adding Dabo base classes to your form; this will allow you to create custom classes that use whatever controls you like, and drop them on a form just like you do the base class controls.
-- Ed Leafe -- http://leafe.com -- http://dabodev.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
