For a front-end application broken down in a MV* manner, should I have models dedicated to UI logic?
I am not talking about simple UI logic like clicking a button directs you to another page, but where one action may result in several different of behavior depending on current application state, and may also trigger response in other parts of the application. Currently my view publishes all UI event so the response can be delegated to other parts. The problem is which other part? In order to avoid writing ‘fat’ controllers that hold arbitrary amount of domain logic, I thought it might be nice to have a non-persistent object that models UI behavior, but am not sure if this makes sense or if I am just pushing the problem around and being object-happy?
Where do the parser and service objects fit in MVC?
Do NSURLConnection service objects and XML/JSON parser objects fall within the controller layer or the model layer? Why?
Should one declare alternative response types (e.g. JSON) in Rails controller actions even if not utilising them?
Just wondering what the accepted convention is for Rails controller design. Currently, every controller in my app that I’ve written it set up to send a JSON response when necessary. Thing is, I only ever utilse HTML responses in my app. So is it a good idea to have them defined?
Is the use of security conditionals in a view a violation of MVC?
Often what’s displayed to a user (e.g. on a web page) will be based partly on security checks. I usually consider user-level / ACL security to be part of the business logic of a system. If a view explicitly checks security to conditionally display UI elements, is it violating MVC by containing business logic?
In JSF where do objects like PhaseListeners fit in the MVC pattern?
When it comes to JSF, I’ve had trouble distinguishing where certain objects I create fit into the overall MVC pattern. The View is simple enough since that’s handled by the .xhtml template but when it comes to objects like:
Migrating legacy procedural code to MVC without rewriting [closed]
It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 11 years ago. I recently started working on a PHP application […]
MVC 3 Page design; split pages into Many partials?
I am currently working on an MVC 3 Web app project where I need to display a lot of information on the front page. I am relatively new at web page layout and design so I have hit a wall in terms of how to structure the code behind for this page.
MVCS – Model View Controller Store
I recently decided to start learning iOS Development, and to this end I’ve been reading iOS Programming: The Big Nerd Ranch Guide. In the book the authors describe a design pattern MVCS – Model-View-Controller-Store, the basic idea being that since many applications make use of multiple external sources of data keeping the request logic in the controller can get very messy, instead the authors propose that moving all the request logic out of the controller and into a separate object.
Service layer design
I am developing an MVC website in PHP, and for the first time, I would like to implement a service layer. I have some design considerations I would like to get some advice on. The backend will by no means be a large enterprise system, so I am looking to keep things relatively simple while still leveraging the benefits of a service layer.
MVC exposes database primary keys?
I’m going through a MVC tutorial, and I notice that convention seems to be to expose a tables primary key on detail pages/urls (ie. /Movies/Details/5 as an example from the tutorial).