I'm looking to re-write a native wxPython application into one that is split between Dabo and Django. Dabo for local heads-down users and Django for offsite surfers.
Some questions 1. How difficult is it to re-use things designed in the ClassDesigner? I'd love being able to use the GUI designer - it might even make sizers tolerable. But I have *dozens* of nearly-identical screens. Example: a grid from which the user picks a record to edit but with variations in number of columns, headers, column formatting. I don't want to have to start each one from scratch when plugging in a few parameters in the right spot could have it done once in a reusable fashion. 2. What if I wanted to use a different "model" underneath the UI part of Dabo? What do I lose if I give up bizObjects in favor of, say, SQLAlchemy or the model from Django? It probably goes without saying that having one model is better than two. 3. How does one get started with Dabo? I've watched several of the screencasts and have read a lot at the wiki, but I'm still looking for the "Get Started With Dabo Building Your First End-To-End Real Application" tutorial. Thanks, Michael _______________________________________________ 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]
