On Thursday 27 August 2009 03:06:10 pm [email protected] wrote: > And furthermore, how would we substitute our own forms created in the CD, > since these are not python code but rather cdxml? Can we use the > dabo.ui.createForm function somehow? > > And as a more general question, what's the best route for us to pursue > knitting things together -- we're definitely looking for "MDI" style > application, with a main form with some kind of splash screen, and forms > that are called from the menu. More or less in the fashion of the app > wizard. So the app wizard might be one model. I also see that quickstart > creates a simple structure for an application. Should we build on that, > rather than the appwizard? >
I don't use appwizard and really haven't looked at the code in a very long time. Therefore can't help with those appwizard questions. to use a cdxml file: frm = dabo.ui.createform(NameOfFile) frm.show() I hand code my forms for a number of different reasons. But many of us combine cdxml and hand coded forms in an app. So the answer to the last question is - it depends. For me I would hand code the forms that need subclassed controls or special methods to handle the app's needs. Then use the ClassDesigner for any forms that do not require anything special. But I would start with 'quickstart' simple structure. I'm sure other's will have a different take on how to move forward. Johnf _______________________________________________ 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/[email protected]
