logic of button to be disabled or not in mvc

Posted by rod on Stack Overflow See other posts from Stack Overflow or by rod
Published on 2010-04-16T03:45:08Z Indexed on 2010/04/16 3:53 UTC
Read the original article Hit count: 343

Hi All,

Here's an excerpt from a book I'm reading about application design with MVC:

Ideally, the view is so simple and logic-free as to need virtually no testing. Users (and developers before users) can reasonably test the view by simply looking at the pixels on the screen. Anything else beyond pure graphical rendering should ideally be taken out of the view and placed in the controller and model. This includes, for example, the logic that determines whether a certain button should be enabled or grayed out at some point.

what does the bold statement mean to you? what would this look like?

thanks, rod.

© Stack Overflow or respective owner

Related posts about asp.net-mvc

Related posts about design-patterns