On Dec 11, 2008, at 1:59 PM, Frederick Cheung wrote:
> On 11 Dec 2008, at 12:55, Martijn Vos wrote:
>> On Dec 11, 2008, at 1:19 PM, Frederick Cheung wrote:
>>> On 11 Dec 2008, at 11:37, Martijn Vos wrote:
>>>> On Dec 11, 2008, at 12:08 PM, Sijo Kg wrote:
>>>>>
>>>>> There is an option prompt like
>>>>> <%= select("model", "status_id", Status.find(:all).collect {|p| [
>>>>> p.name, p.id ] },options ={:prompt => "<< Select any >>"}) %>
>>>>>
>>>>> I think you can do similarly
>>>>
>>>> Doesn't seem to work in date_select. And throwing away the
>>>> power of date_select in order to handle everything myself seems
>>>> like a bad idea. I'd rather add this functionality to date_select.
>>>>
>>> If you're worrying about good UI, date_select is pretty horrible
>>> anyway. Would be something of a lipstick on a pig thing.
>>
>> Until I needed to add a nil option, date_select worked fine for
>> me. What's so wrong with it (other than this particular issue)?
>> And is there a better alternative availlable?
>
> People have a hard time working with stuff like '20th december'. Is
> that a saturday or a sunday etc... Or they're thinking in terms of
> 'next monday' and things like that, in which case it's a lot simpler
> if they don't have to do the date maths themselves.
Point taken. But I'm using date_select for birth dates, so for me
days of the week aren't much of an issue. I just don't want to
force a default birth date on people who are unwilling to provide
it. The day-month-year combo of date_select seems perfect for me
so far, except for the inability to provide a nice text for the
empty value.
Martijn.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
