edwinmoss / calendar_date_select
watch download tarball
public
Forks68Right
Watchers2Right
Fork of timcharper/calendar_date_select
Description: A popular and flexible JavaScript DatePicker for RubyOnRails (and others)
Homepage: http://code.google.com/p/calendardateselect/
Clone URL: git://github.com/edwinmoss/calendar_date_select.git 
Merge branch 'core'
Edwin Moss (author)
Thu Feb 19 10:38:49 -0800 2009
commit  e411f879880c3a08ec69e95895df146db1e7ba83
tree    9f1f2bfd1da19463c5f024c13946cbbaa6cd3a03
parent  71ec974bf96c332b9c171488ac2a77b406740ee0 parent  b63886b73d25bbebd482abbfdacc29bac1b09f90
name age
history
message
file .gitignore Sun Nov 30 01:00:01 -0800 2008 update gitignore to ignore doc [timcharper]
file History.txt Thu Feb 19 10:28:19 -0800 2009 Merge with coreteam. [Edwin Moss]
file MIT-LICENSE Mon Sep 03 03:04:35 -0700 2007 fixed spelling on the license file git-svn-id:... [timcharper]
file Manifest.txt Sun Nov 30 00:10:55 -0800 2008 updated to include new files [timcharper]
file Rakefile Thu Feb 19 10:28:19 -0800 2009 Merge with coreteam. [Edwin Moss]
file Readme.txt Tue Apr 28 11:34:14 -0700 2009 Renamed Readme.txt to README.txt for case sensi... [mhaley]
file calendar_date_select.gemspec Sat Nov 22 23:08:34 -0800 2008 Cleaning up to prepare for ruby-forge release ... [timcharper]
file init.rb Sat Nov 22 23:08:34 -0800 2008 Cleaning up to prepare for ruby-forge release ... [timcharper]
directory js_test/ Sun Apr 06 01:57:13 -0700 2008 updated to reflect the movement of closeOnClick... [timcharper]
directory lib/ Thu Jan 08 11:33:09 -0800 2009 :format is not a valid option for calendar_date... [timcharper]
directory public/ Thu Feb 19 10:38:49 -0800 2009 Merge branch 'core' Conflicts: lib/calendar_d... [Edwin Moss]
directory spec/ Thu Jan 08 11:33:18 -0800 2009 includes_helper spec [timcharper]
Readme.txt
= CalendarDateSelect

http://code.google.com/p/calendardateselect/

== Examples

"See a demo here":http://electronicholas.com/calendar

== Submitting patches

Please take care to do the following:

* Clean up your patch (don't send a patch bomb with a hundred features in one)
* Write test cases!
* As a general rule of thumb, think of ways to make things more general purpose than specific.