Ed Leafe wrote:
>       FWIW, the AppWizard is not how you should be coding anything but the  
> most basic maintenance apps. It is a tool to get a basic CRUD app up  
> and running with very little effort. Perhaps it's just me, but it  
> seems like you are trying to make it into all things for all people  
> in all cases, and that simply isn't possible.
> 
>       If you can't make your AppWizard-generated code do what you want,  
> then that's a very good sign that you've outgrown it, and can start  
> creating real applications.

Ed and I agree on the AppWizard having limited usefulness WRT the code 
it generates. However, I happen to believe that the structure it starts 
you with, and the datanav framework that it subclasses, are great starts 
for highly capable and scalable customized applications. I'm basing all 
my applications around it, and haven't hit any roadblocks yet. There are 
forms where the datanav stuff gets in the way, but nothing stops me from 
creating a customized form or dialog from scratch and putting into the app.

I don't regenerate application code over and over again. I generate 
once, modify, add, and delete stuff, and from then on I maintain the app 
manually. IOW, I use the appwizard output in the spirit it was intended 
to be used.

Once we have appwizard ui generating cdxml files that can be visually 
modified in the class designer, the power of this approach will be even 
more apparent. One of the greatest timesinks for me is not coding my 
business rules, but manually coding my sizer-based ui-designs.

-- 
pkm ~ http://paulmcnett.com


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev

Reply via email to