Paul McNett wrote: >>> Yes, you are correct. That's what I get for responding on the fly! > > I find myself surmising what I'm doing differently in my code. I've > never found a need for afterInitAll(). > > Paul > > If I understand correctly, you hand code instead of using Class Designer, so you can deal with it as part of the original setup when you instantiate the controls.
Right now I really don't want to hand code unless I have to. To get done what I have to get done I need RAD tools like Class Designer. I don't know Python except at a beginner's level. I don't want to deal with Tier 1 and 3 except with RAD tools. Now Tier 2, Biz objects that's what I deal with the best and you guys have made it so that the drudgery of the UI code is fast and painless with Class Designer, when the learning curve is over, and there are all the RAD tools you could ever want for the Database Tier. So having to do things, to have most of the UI done for me with a GUI RAD tool, in different places is worth it. So if I find I can stick something in afterInitAll() and it works without a gigantic performance hit, I'm going to choose that way. The great thing is Dabo let's you do it your way and I can do it my way. The philosophical differences between you and Ed, about this subject has been excellent reading on the web sites and mailing lists. It creates a much better product. Thanks again for the nice framework and tools Paul McNary [EMAIL PROTECTED] _______________________________________________ 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]
