On 12/19/06, Paul McNett <[EMAIL PROTECTED]> wrote: > In talking to people, sometimes they discuss Dabo in terms of what they > saw in the AppWizard output, but are you positive that you are reading > their assumptions correctly that they believe their app must look and > work just like that? Because if I were that person, I'd come away going > "ick, Dabo isn't general enough for me". > > So, *if* your assumption is true, we have a problem to solve.
As a newbie pondering, that is some of my reaction after playing with AppWizard--except that I went to a presentation given by Ed on dabo and know that there is more to it than just generating, for example. data entry screens. (I've been hacking on a generated data entry page class to get a feel for things). > and other things we don't do anymore. Also, when it began it became a > testing area for areas in dabo that weren't very mature yet (dGrid). yeah. I'm playing around with it to get a feel for the geometry management. I'd like to see better geometry management from dabo. > But AppWizard is a different story. I have a hunch I may fall into the > 'misusing' camp myself, because I am able to take the generated code and > work it into any conceivable data app. See, but this is too limited. If that's all it does then why not use vanilla python? Explain the added value for the effort it takes to adapt dabo. the automation has to be worth it. -- sheila _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
