* Inputs with legends as labels now got class "label" on the legend to make the styling of these much easier. * Inputs with legends as labels now wraps a label instead of a span, and the label is "connected" (with the "for" HTML attribute) to the first of the wrapped inputs - clicking label gives focus to this input. Reasons: Better form accessibility/usability, and is semantically more correct. * Removed: :as_span-option for the Formtastic label helper - not needed anymore. Closes #101.
…e instructions on plugin and gem installation. Closes #118.
…alue] as well - for consistency, i.e. avoiding confusion.
…y errors a bit smoother. Also added support for Jeweler::GemcutterTasks.
…instead on the old GitHub one - to avoid any confusion.
… run and pass on 1.8, 1.9.1, and jruby.
…n of the select input, e.g. form.input :rating, :as => :select, :collection => 1..5. Added specs for both ranges, and explicit array values which was lacking. Closes #115.
…es similar to the recent I18n in Ruby 1.9+), but also a good convention: Formtastic => ::Formtastic
…ing the only private method to protected for consistency.
…id legend - the options (:name/:title) way works still, and got higher priority. Closes #106.
…Symbols for convention - in a way that works this time.
…s (especially a issue in Ruby 1.9). Closes #109.
…nt to write tests for a deprecation, silence/enable them in a before/after block
…an do that, right?
… string_input_spec.rb, etc
…tion loop specs
…all input specs now, which has beefed coverage right up
…he path through the code and which :as options map to which methods inside the code. More to come, but I'm trying to make the code more accessible and readable.
…hey pass on my machine and runcoderun, no idea if they passed for the original author, but everything looks okay
E.g. f.input :author, :group_by => :continent It works a bit different compared to the #grouped_options_select method of Rails. It will collect #continent from each author instead of collecting authors from all continents. Under the cover it will use the Rails implementation however. The Rails implementation combined with ActiveRecord causes an n + 1 query problem. I have tried to minimize this but the issue remains.
…ed with the :selected option, just like :select inputs, resolving issue #112.