winforms - C#: How to cleverly design a GUI for a Desktop Application with encapsulation in mind -


I am developing a desktop application, which has grown up with the mainframe. Many containers have many controls on different levels (split container, tabpeps, panel).

Now I want to repeat this class by separating all the controller codes responsible for data binding & amp; Clearing controls or taking user interaction in different controller classes

[edit]

purpose

The purpose of this application is called order ) And track their position (called joyitem). Every job is related to a customer, each jobtime has an article (Joyitems contain information that is specific to the article's manufacturing process, so this article is wrapping up) Jobs, Jobitim, Customer and Article in dynamic Properties (Basic Key / Value Coupling), which are managed by a property manager class.

Architecture

My application is divided into 2 main projects: 3 LinqToSQL DataContext Classes have a data model in the core:

    • >

    There is a XyzManager class for each datacontent class, which provides the LinqToSQL object in one, the collection of GUI, the LinuxCTOQL data source to Encore The T. It also handles the creation, deletion and modification of its related datacontext types.

    Then I have a GUI project, naturally there are some additional forms for a main look and options such as stuff. As of now, my GUI project maintains a reference for each XS Manager class and & amp; Manager sets the data as user interactive directive through sections, which contain all the controller logic.

    I have put the most independent argument for this in a stable utility class outside the main form class, but it is less than an ideal approach which I think.

    [/ edit]

    This is my first big desktop application and I have a hard time getting a GUI. As of now, all the controller codes responsible for dealing with user interaction remain within the mainform class.

    I know about the MVC pattern but I'm not sure its current design at C # WinForm.

    My custom code alone is more than 2400 line code, not automatic form generating code, with increasing trend. I want to do it again, but how can I solve it more elegant way, as I have lost.

For small-scale applications, you should take a look at Model-View-Presenter (MVP) The best way to do MVP (in my opinion) is a good presentation:


Comments

Post a Comment