Jeremy Bush

> injecting modules into things at runtime is all kinds of bad. I hear you on that. I think doing DCI with decorators is just as fine though. I'm in...

> looking through the code suggests that @garybernhardt did mean for users to use ValidationError externally. I think that's where I got the idea. :) > Raptor (as it stands...

> Any ideas about the validation stuff? ValidationError can definitely go if there's a better way to do it, and especially if that way makes feeding errors to presenters easier....

Basically what I think I want is something that will take the response of the delegator and put it into the presenter somehow. The response would either be an exception,...

I'm of the opinion that the template (what you call the view, i think) should get _everything_ from the presenter (and nowhere else). It provides a clear separation between view...

Yep, when using mustache, I have a layout class that contains all this logic, and my pages extend this. In classical MVC, I'd pass that info in via the controller....

I'm a huge fan of that :) When initially looking into raptor I learned about Tilt, but was very disappointed that mustache wasn't available. It's basically a really nice presenter...

Yeah. I don't really like `content_for` personally. I feel like it's just a hack around the fact there's no real class behind the template.

I think a lot of the objections are because it doesn't work like erb. You can't use native ruby things in the template like people are used to (for links,...

On another topic related to some of the the original posts here, I was able to write some basic error validation and get it displaying in the view: ``` ruby...