Designing Versatile Add/Edit Forms & Pages
Posted on 2000-02-29
This is more of an opinion question than a "need help" type question. I'm new to the visual programming world and I'm beginning to learn to work with classes ... subclassing, etc.
I've noticed that Microsoft uses page frames very heavily in their applications. Usually, they'll have a page frame with multiple pages with editable fields on each page. They'll have one cancel and one apply button on the page frame that applies to all pages. Each page may or may not have it's own add, remove or properties buttons.
In designing apps, is their a tendancy to create a custom page frame that includes an apply, cancel and quit button and then just hide them if you don't need them, or to create a button group of cancel, apply and quit buttons and place that button group as needed or do most folks just add those buttons individually as they need them?
If there is someone who has developed a method of implementing a "default" set of cancel, apply, quit buttons, I'd be interested in hearing how you implement a default set of buttons to work with a page frame where each page may be dealing with a different table.
I'd be interested in getting a few different opinions on this so I'm willing to give out points to more than one xpert (if I'm able to).
Thanks for the help.