Three doc questions about draper

[jcasimir]

Jay,

Thanks for asking questions!

1. I'm hesitant to say it's ready. I'm very thankful to everyone that's trying it out and helping me polish things up. Before I declare it truly production ready I'd like to do more performance analysis, freeze a 1.0 feature set, and get have some of the code scrutinized.
2. I'm draw a line between presenter and decorator, mostly for historical reasons. To me, a decorator is part of the view layer. Most people use presenter the same way, but I use presenter to refer to "plain old ruby objects" which are wrappers around multiple domain models at the data layer. So, going really "all-in," I might have multiple AR models which are wrapped in a decorator proxy at the model layer, then at the view layer wrap it with a decorator. Sounds awesome and crazy.
3. That's interesting. I don't see why not. The only thing I can think of that would possibly cause an issue is the self.model_name in base.rb where we call ActiveModel::Name.new(model_class) -- but I did a quick test on Rails 3 / 1.9.2 and it was fine.

[jaylevitt]

On #2: That makes sense. I'd suggest adding something to the doc, explaining that - and, if you want to get into it a bit more, you can also Google some discussions about the difference between Presenter and Conductor (opinions seem to vary, and I have no idea who's right). It'd be good to give draper the Google juice for "rails presenter"; I've been Googling that once a week forever, every time I run into some ugly view logic.

[jcasimir]

I'm going to think about the decorator/presenter thing more but close the issue for now. Please comment if you have any remaining questions.