Sorry Nate I disagree with respect of extending AppWizard. I would like to see the AppWizard dropped. Let me say I use AppWizard everytime I want to test the data interfaces but that's all.
When Yair Alan Griver published CodeBook he provided a sample invoice example that used most of the features of a 3 tier design. I wonder if a wiki tutorial on creating an invoice would work as our tool for newbies? I like tutorials that start off with simple screens/examples and move to the complex. Each of the examples would teach a part of Dabo. I would not be quick to start with the GUI either. Understanding the role of bizObjects does not require a GUI form. John On Monday 18 December 2006 09:50, Nate Lowrie wrote: > On 12/18/06, Paul McNett <[EMAIL PROTECTED]> wrote: > > Ed Leafe wrote: > > > On Dec 17, 2006, at 10:54 PM, Paul McNett wrote: > > >> I don't regret it, but would love to see an alternative appwizard to > > >> learn from. For now, the current one really does seem to fill all my > > >> basic needs. > > An alternative app wizard? What exactly would it do? I think a > better option for learning might be a tutorial or screencast on how to > take an Application generated by the App Wizard and expand it's > capabilities > > > > That's part of the problem, too. It really is a very useful tool. > > > That makes it easier for people to expect it to do whatever they want > > > instead of understanding its limits and making the correct choice > > > beforehand. > > That's something that you are just going to have to deal with. > Nowadays, more and more people expect a single magic app to just spit > out a splitting image of what they are thinking an app should be in > their minds. We can created a dozen articles, wiki pages, and > screencasts highlighting the limitations of the app wizard and there > will still be people out there that will ask why the app wizard > doesn't do this or bad mouth dabo because the app wizard couldn't do > that. It's sad but I've seen it happen. > > > IOW, we are touching on good 'ol human nature! :) > > > > It takes experience with a thing to determine the limitations, and how > > to possibly improve the thing. We'll need to keep telling people over > > and over again what the intent of the AppWizard is, and what class of > > problems it potentially solves. Eventually perhaps we can point to a > > wiki page (someone want to put that together, complete with the nuance > > between our opinions on the scalability of AppWizard-generated apps?) > > This is good. I think that there should probably be several wiki > entries/screencasts/articles on: > > 1) Intent of App Wizard and what it does. > 2) Limitations of App Wizard > 3) Scalability of App Wizard-generated apps > 4) Customizing and expanding an App Wizard-generated App > > There's my $.02. If no one takes this, eventually I will get around to it. > > > -- > > pkm ~ http://paulmcnett.com > > > > > > _______________________________________________ > > Post Messages to: [email protected] > > Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev > > _______________________________________________ > Post Messages to: [email protected] > Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
