months = ['Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec']
labels = []
0.upto(5) do |x|
  labels.unshift(months[Time.now.months_ago(x).month-1])
end

Which I think is pretty neat, especially remembering what a pain it was in Perl last time I had to do it……..

Hopefully the first release of the plugin should not to be too far away and will add a little functionality to the existing code.

One of the things I hope we can develop is a nice search interface to the table. I had to do this with the perl Catalyst Framework earlier this year and I think the general approach could work quite well.

The approach I took was to define some (3 in fact) search tags which inherited from the basic html tags. So instead of just a “textfield” I had a “like_textfield”, or a “comparator_textfield”. This allowed me to easily add search functionality for each field in a model. This provides an exceptional comprehensive search system.

To clarify what I mean it is probably easiest to look at the sql mappings the tags produced:

1. “comparator_textfield” – used for numerical values, comprises two fields, one a select containing ”<”, ”>” and ”=” and a second for the value. So selecting ”>” and entering “2” in the field would translate to conditions such as “where x < 2”

1. “like_textfield” – for full text search, comprises single textfield with a hidden “like” modifier field. So entering “scott rutherford” into the search would give “where x like ‘scott” or x like ‘rutherford’”

1. ‘comparator_datefield’ – this was used for searching on dates, so like the numerical case this comprised 2 fields. The first held the modifiers “before”, “on”, “after” and the second drop downs to define the required date. This leads to sql like “where 20060506 < date”, etc.

Rails lends itself very nicely to this approach with the concept of helpers being fundamental to the framework. I feel it would be pretty easy to create helpers for these new search fields and then simply generate a form for a model on the fly as I did (using Richard’s existing helper code) with the scaffold plugin. The interesting bit comes in translating all of this into conditions for ActiveRecord, then storing it for the paging and sorting.

The easiest way to achieve this search persistence I feel is to just use the session object to store the current search, in fact that is the method I used previously and it seemed to work out.

Putting all that together would certainly lead to a radically different search to the “Live” search boxes that are all the rage currently, but my experience of working with tabulated data is that a simple text search is not enough.

At the moment I am beginning to think that this could be a plugin in its own right really and that if it is designed with AjaxScaffold in mind that then the search could potentially be made pluggable. Also of course that would mean you could just generate search forms for standard tables as well as Ajax ones (if that is for some strange reason you didn’t want your tables to look really cool…..).