Option yearRange is needed for datepicker

[dima4p]

And most probably for the portotype version.
You see, it is strange to have the range 2001..2021 for the birthday year of the user.

[leikind]

any ideas about the API and the way it should look like?

[dima4p]

I think, the option for #column should be created. I suggest to make it indifferent on the java-script used, will it be datepicker, calendarview, or something else. It should take the hash that is to be translated to JS object and passed to the JS call.
It may be named :js_options, so in my case it will be like the following for the ruby 1.8:
g.column :attribute_name => 'born_on',
:js_options => {:changeMonth => true, :changeYear => true, :yearRange => '-120:+0', :defaultDate => '-30y'}

[dima4p]

P.S. I know you pass changeMonth and changeYear, but maybe someone will want it to be false.

[leikind]

The solution is very basic: a88a750

There is a default year range for all datepickers in the config file. Providing WiceGrid configuration API to set up each grid seems redundant when one can easily change the range with javascript:

$( ".hasDatepicker" ).datepicker( "option", "yearRange", "2000:2042" );

[dima4p]

What if different ranges are needed, say for :date_of_birth and :passport_valid_tilll?

[leikind]

Then you use the aforementioned javascript with DOM IDs to target specific datepickers . There is no need for additional API when using datepicker( "option", param, value ) is a perfectly valid jQuery way.