Thinking of Design patterns

     Recently, I work on design and coding in UI for a database query requirement, I realized that what the Design Patterns palys it's role in my coding.

     First, actions of UI in Windows System, message mapping action and response transactions must be resonable aranged. For example, these are four relative query condition in UI, two must select from dropdown list, one may select from dropdown list or input by user, and the other one must input by user. User click query for query action. Now, How many actions will this compones occupt? What kinds of actions every compones need to response? And how to response? Besides, string input by users must be check for avilable. When check and when update the combo or edit value to the member value?

     Second, the UI function should not confuse with the transation logical functions, that means you need to create new class for this UI transaction logic handle. This new class may have one or more member value and functions, and which can call by UI moudle, and which should be private use may make me hard to design.

     Others, This new class should by the only one communicate with the UI function how data construct and destruct still need time to think of.

     So, I realize the importance of the design paterns.

 

     The book writen by Erich Gamma named <Design Patterns> should be a readable book in this field.

     Buy it and enjoy it.