Any recommendation for a good enough Winforms GUI design? -
i developing mid-size application vb2008. better test application following mvp/supervising controller approach.
my question is: recommendations separate responsibilites? far i've come winform instance of controller , instance of class. controls updated via databinding
the problem i'm not sure write responsibilites (let's validation, report creation, queries , on) inside class? in separate class?
is there small example of clean winform class design point me?
i suggest spend time reading jeremy millers 'build own cab' series of posts feel might like/need implement application becomes more complex.
Comments
Post a Comment