Hello Everyone,
I am having a hard time understanding how to implement MVP in winforms with
custom controls. I am attempting to make use of TDD using nUnit for my
tests. Do any of you have a list of links to direct me to?
It seems to me that custom controls are mini views that are used in a larger
composite view. Since control creation occurs on during form
initialization, how does the view get hooked into place?
When transitioning from view to view, the presenter needs to create or
resuse other presenters that then create or resuse other views. What is a
good mechanism for managing that workflow?
When populating a list control from a presenter, how is this best done
without holding a refernce to system.windows. forms in the presenter
libraries and keep the autonomy for web/win UI's?
Perhaps my questions are too narrowed in scope and a better understanding of
the pattern will aide me in development.
I am working on a prototype that currently presents a user login, a main
form that offers the user the ability to manage users and groups. It is not
clear how to transistion from view to view without something knowing more
about either the UI or the Presentation layers than I feel it should.
my views:
UserLogin -- Supply username and password, login or cancel
Main (holds list of users and groups in a custom control) -- Menu items to
manage user and groups
AddUser -- Initially create a new user
EditUser -- Edit a user, assign to groups
ChangePassword -- User can change password (userid, old password, new
password, confirm password.
AddGroup -- Initially create a new group
EditGroup -- Edit a group and assign users to the group
Thanks in Advance
I am having a hard time understanding how to implement MVP in winforms with
custom controls. I am attempting to make use of TDD using nUnit for my
tests. Do any of you have a list of links to direct me to?
It seems to me that custom controls are mini views that are used in a larger
composite view. Since control creation occurs on during form
initialization, how does the view get hooked into place?
When transitioning from view to view, the presenter needs to create or
resuse other presenters that then create or resuse other views. What is a
good mechanism for managing that workflow?
When populating a list control from a presenter, how is this best done
without holding a refernce to system.windows. forms in the presenter
libraries and keep the autonomy for web/win UI's?
Perhaps my questions are too narrowed in scope and a better understanding of
the pattern will aide me in development.
I am working on a prototype that currently presents a user login, a main
form that offers the user the ability to manage users and groups. It is not
clear how to transistion from view to view without something knowing more
about either the UI or the Presentation layers than I feel it should.
my views:
UserLogin -- Supply username and password, login or cancel
Main (holds list of users and groups in a custom control) -- Menu items to
manage user and groups
AddUser -- Initially create a new user
EditUser -- Edit a user, assign to groups
ChangePassword -- User can change password (userid, old password, new
password, confirm password.
AddGroup -- Initially create a new group
EditGroup -- Edit a group and assign users to the group
Thanks in Advance