[Boulder-Denver Ruby Group] re-inventing components

[Tony Arcieri]

That was my impression of Stencils as well... that it was moving Rails more
towards a component-oriented approach, although for whatever reason (DHH?)
components have been frowned upon by the Rails community, despite their
success in frameworks like WebObjects (which, correct me if I'm wrong, was
the first MVC web framework to use an ORM for abstracting the data model).
Seems like Rails learned a lot of great lessons from WebObjects, but
component-orientation was not one of them.

"There is only one controller in effect at a time in Rails and that
controller's data is, effectively, global for all rendering actions"

This has been a big problem for me, particularly when I'm trying to make
reusable, interactive (AJAX) "widgets" that allow you to have the same
functionality on multiple parts of the site.  A messaging system is one
example.  Until now the solutions have been "use helpers" or
render_component, which seems to be shunned and isn't implemented very well.

I'll certainly check out componentry when you release it.  There's a few
places I could see it being very useful.

-- 
Tony Arcieri
ClickCaster, Inc.
tony at clickcaster.com
720-227-0129 ext. 202

On 5/18/07, ara.t.howard < ara.t.howard at gmail.com> wrote:
>
> i'd love feedback from the community
>
>         http://drawohara.tumblr.com/post/2070878
>
> cheers
>
> -a
> --
> we can deny everything, except that we have the possibility of being
> better. simply reflect on that.
> h.h. the 14th dalai lama
>
>
>
> _______________________________________________
> Bdrg-members mailing list
> Bdrg-members at rubyforge.org
> http://rubyforge.org/mailman/listinfo/bdrg-members
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/bdrg-members/attachments/20070518/2dadb80f/attachment-0001.html