>>snip<
>
>>Doug,
>>
>>I've had one big app class that had everything in it. Now, I'm rethinking this, based on my reading of "Effective Techniques".
>
>Hi Craig!
>
>Say, what are you concluding or thinking about?
>
>Right now, in my puny brain, I'm thinking of having several objects like Security, Form Management and so forth. What to do from there, in terms of flexibility and durability is what I'm chewing on in my mind. I'm
keenly aware that this is one of those kinds of decisions that will have long long term impact and I do not want to fall into the trap of having to defend my decision solely on the basis of the notion that it was my decision. *g* I'd really like to get the different strengths and weaknesses on the table from others who may have implemented 'Approach X' or 'Approach Y' if possible.
>
>Soooo.. What is your approach going to be? *g* IOW, what gems have you extracted from the "Effective Techniques" book?
>
>Best,
>
>DD
The way I have things set up now, I have one big app object. It has methods for opening forms, handling environment settings, etc. I'm gonna break it down into different objects, so there will be a separate class for form management, menus, toolbars, environment, etc. I'm about finished with Effective Techniques, then I'm digging into Advanced OOP. Once I'm done with that, I'll begin to rebuild my framework.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer