The controller is busy deciding which view the (to?) render and
coordinating these (the?) other efforts.
Once the model is ready, the controller passes them (it?) into the View
() method, transfer(r)ing them (it?) to the view (2). - Seems that
only one should be left either "passes it into the View() method" or
"transferring it to the view".
Developers can confidently maintain even the "gnarliest" screens as
long as the presentation model is designed well
At the bottom line:
we can levage ASP.NET MVC 2 features to work with a strong input
model. - It the word "levage" correct?
Figure 2.2 A form for user input. It is a bit strange that "Active"
label is displayed over the checkbox. It might be better to show the
code which will display the label right after checkbox
[ ] Active.
However this is not a subject of the discussion.
We('ll) cover these helpers in depth in Chapter 3.
The end user can see a list of customer summaries, but they may also
modify the status of the customer, checking the box is (if?) the user
should be activated.
Listing 2.8 A combined model. - #3 explanation is missed.
I have one comment about a piece of code.
2.5.2 Working with the input model.
This code shows an action signature which takes a List of
public ViewResult Save
(List<CustomerSummary.CustomerSummaryInput> input) #1
I assume that you would not just be setting the View's Model to input,
correct? You might put a comment such as //todo: call method to handle
user input, or simply mock up that method and pass the input variable.