Thursday, April 24, 2014

Presenter Object

http://robots.thoughtbot.com/post/13641910701/ti dy-views-and-beyond-with-decorators

http://blog.steveklabnik.com/posts/2011-09-09-better-ruby-presenters
   I hate not understanding a joke: Dijkstra's Algorithm

 

http://railscasts.com/episodes/287-presenters-from-scratch

http://stackoverflow.com/questions/20503445/using-presenters-ryan-bates-style-without-an-associated-model

http://eewang.github.io/blog/2013/09/26/presenting-the-rails-presenter-pattern/

Presenter is a Design Pattern
http://pivotallabs.com/presenter-sanity/
http://stackoverflow.com/questions/7860301/rails-patterns-decorator-vs-presenter

http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93presenter
Model–view–presenter (MVP) is a derivative of the model–view–controller (MVC) architectural pattern, also used mostly for building user interfaces.
In MVP the presenter assumes the functionality of the "middle-man" (played by the controller in MVC, although it must not be assumed that the presenter and controller play the same role). In MVP, all presentation logic is pushed to the presenter. Eventually, the model becomes strictly a domain model. 
(The domain model is a conceptual model of all the topics related to a specific problem. It describes the various entities, their attributes, roles, and relationships, plus the constraints that govern the problem domain.) http://en.wikipedia.org/wiki/Domain_model

Presenter and Decorator in Rails Slideshare

http://www.slideshare.net/thaichor/presenter-and-decorator-in-rails

Now to take a break with a Bundler Core Team favorite, Bee and PuupyCat!



No comments:

Post a Comment