Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have one abstract class and many child classes. In child classes are from 2 to 20 members which must be filled by user. What the best way to do this using OOP? Make form for each child class? Or hide and unhide many input elements and labels? Is there some best way? I using WPF and C#
The answer depends on what it is that your app actually does. UI should be be designed with the user in mind, not with the underlying data structure. The user probably doesn’t know what the underlying data structures are, and probably doesn’t care. The UI should be implemented in the way that makes it easiest for a user to use. (This is rarely a simple task.)
It’s not a good practice to tightly couple the UI to the data. There are several architectures you can employ to make sure the UI and data stay decoupled: MVC, MVP, MVVM, etc.
http://en.wikipedia.org/wiki/Model-View-Controller
http://en.wikipedia.org/wiki/Model_View_Presenter
http://en.wikipedia.org/wiki/Model_View_ViewModel
A more specific answer to your question, using one of the above architectures, you’ll probably want a “form” (typically called a “view”) for each class.