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.
At a conceptual level (not platform/framework specific), how should components like toolbars and menus (and the commands they contain) be implemented in a desktop application that uses the MVC pattern, with minimum coupling & maximum code reuse?
Generally, commands are bound to menu items, toolbar buttons etc. would expose following information to controls:
If you prefer to use MVC pattern, not MVVM, you probably being hard to determine where command logic would be placed. You may expose these information via model, or you may place corresponding code in controller.
If you use component-based UI, like .NET WPF/WindowsForms/Silverlight etc., you probably may create interface for the command that exposes all listed properties, and create custom controls inherited from MenuItem, ToolbarButton etc. that handles information from such interface.