any reason you're using a base class instead of a module, for the base presenter? i'm still pretty early in my rails career (~1yr), but I thought "the rails way" was to use modules instead of inheritance.
it's interesting to hear you say why you suggest not using notifications for app logic. the reasons you listed for not using it are the exact reasons that i want to use it for my app logic. :)
i've got a blog post from yesterday that talks about the scenario that I'm trying to solve and how I would have used the event aggregator pattern if i were building a .net / winforms application. the notifications system is an event aggregator built right into rails, and is perfect for what I need.
I wrote a couple of articles and gave a talk on this last year, specifically with backbone:
http://lostechies.com/derickbailey/2011/09/26/seo-and-accessibility-with-html5-pushstate-part-1-introducing-pushstate/
http://lostechies.com/derickbailey/2011/09/26/seo-and-accessibility-with-html5-pushstate-part-2-progressive-enhancement-with-backbone-js/
and
http://lostechies.com/derickbailey/2011/10/06/seo-and-accessibility-with-html5-pushstate-part-3-the-video/
any reason you're using a base class instead of a module, for the base presenter? i'm still pretty early in my rails career (~1yr), but I thought "the rails way" was to use modules instead of inheritance.
it's interesting to hear you say why you suggest not using notifications for app logic. the reasons you listed for not using it are the exact reasons that i want to use it for my app logic. :)
i've got a blog post from yesterday that talks about the scenario that I'm trying to solve and how I would have used the event aggregator pattern if i were building a .net / winforms application. the notifications system is an event aggregator built right into rails, and is perfect for what I need.
if you're interested, here's that blog post: How do you handle simple pub-sub, evented architecture in rails apps?