README.markdown in tableficate-0.3.0 vs README.markdown in tableficate-0.3.1

- old
+ new

@@ -11,25 +11,33 @@ gem 'tableficate', '~>0.3.0' ## Support -### Ruby -1.9+ +<table> + <tr> + <td><strong>Ruby</strong></td> + <td>1.9</td> + </tr> + <tr> + <td><strong>Rails</strong></td> + <td>3.1</td> + </tr> + <tr> + <td><strong>Database Framework</strong></td> + <td>ActiveRecord</td> + </tr> + <tr> + <td><strong>Templating</strong></td> + <td>Any templating engine can be used. The default theme uses ERB.</td> + </tr> + <tr> + <td><strong>Pagination</strong></td> + <td>Any pagination can be used. The default theme has built-in support for Kaminari and will_paginate.</td> + </tr> +</table> -### Rails -3.1+ - -### Templating -Any templating engine can be used. The default theme uses ERB. - -### Database Framework -ActiveRecord - -### Pagination -Any pagination can be used. The default theme has built-in support for Kaminari and will_paginate. - ## Basic Usage Let's say that we want to create a table that lists active accounts in the system with their time of creation and the name on the account. Our controller: @@ -116,9 +124,11 @@ The theme can then be applied to a table. <%= table_for @records, theme: 'foo' do |t| %> ... <% end %> + +[Find out more about themes.](https://github.com/sei-mi/tableficate/wiki/Custom-Themes) ## Changes Needed to Upgrade From 0.2 1. HTML attributes passed to `table_for` will no longer be passed via the `:html` option. Now all unrecognized options are passed as HTML attributes. This is more consistent with the other functions. 2. In custom templates the `options` attribute is no longer available on all objects that had it. Any options specific to the object have been turned into attributes. For example, `label_options` is now an attribute on filters and `collection` is now an attribute on select, radio and check box filters. All other options will be used as HTML attributes and can be found in the new `attrs` attribute.