Rails - May 2005 - common list for controllers

Hi,

For the project I''m working on I have a large number of tables ( 12 )
which I have created controllers for.  The problem is that after
creating these controllers I have 12 list.rhtml files.

The problem is that the tables need to have the same look/feel and
functionality ( begin able to add/remove columns, sorting on columns,
filtering on row data, etc ).  You can find an example of what I''m
talking about here:

https://rcc.sr.unh.edu/~skk/list.png

I would rather not have to keep changing all 12 of the list.rhtml files
when I find a bug in one, or want to add a new feature in another, etc.

What is the best way to go about doing this?  Has anyone done something
like this is the past?

Thanks,

-- 
==================================================| Steven Knight               
skk-Y5xk1i+vvAw3uPMLIKxrzw@public.gmane.org  |
| UNH Research Computing Center   603-862-3042    |
===================================================

Steven Knight wrote:
> For the project I''m working on I have a large number of tables (
12 )
> which I have created controllers for.  The problem is that after
> creating these controllers I have 12 list.rhtml files.
> [...]
> I would rather not have to keep changing all 12 of the list.rhtml files
> when I find a bug in one, or want to add a new feature in another, etc.
> 
> What is the best way to go about doing this?  Has anyone done something
> like this is the past?
One way would be to use components. Maintain one central list.rhtml and 
then do  render_component(:controller => "maintain_controller",
:action
   => "list")  in the other views.

You should also be able to use partials.

I would chose partials when you have to pass Arrays or other non-trivial 
data (like an id or single string) to the central part and components in 
the other cases. I think components will be easier to cache in the future.