= Marcel Molina: Render with presenter plugin

No one is really improving the view side of things - it's just a really simple templating system.

I want the view to be an object, not this wird stream you evaluate, where you can use all what you are used to

== Presenter pattern

http://martinfowler.com/eaaDev/PassiveScreen.html

I want to have objects for every single view, inheriting from ApplicationPresenter < AbstractPresenter

You can basically just treat Presenters like helpers
At runtime you can use an abitrary presenter as long it fulfills the contract

== Differences from the helper stuff

Everytime you set an instance variable, and you reference that in your view, there is an unpleasant coupling with the controller

expects_attributes :day, :account, :current_user
- Will verify that all the state you expect to be there is there


= Sandstone - a plugginable CMS

None of the existing CMS'es are really able to be integrated into an existing Rails application

Features:
 * Versioning
 * Templating (layouts)

The interesting thing is:
 * Generators

Used for:
 * CMS
 * Blog

The context area accepts ERb right now, but they are planning to WYSIWYG it


= European User Group exchange

http://rug-b.com/wiki/show/FriendlyUserGroupSpeakerExchange


= rspec David Chelimsky


= Liquid by Tobias Lüttge (?)

Completly based on regular expressions
Very user friendly error messages
Very safe, you can let your users edit these templates

You can use liquid as a replacement for erb:
index.html.liquid

Liquid::Template.parse(body).render(assigns)