railssignals / jquery_calendar_date_select forked from timcharper/calendar_date_select

A jQuery version of the popular and flexible JavaScript DatePicker for RubyOnRails (and others)

This URL has Read+Write access

jquery_calendar_date_select / README.txt
100644 59 lines (34 sloc) 1.832 kb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
= jQuery CalendarDateSelect
 
A jQuery based version of the calendardateselect plugin.
 
= Installation
 
  1. script/plugin install git://github.com/railssignals/jquery_calendar_date_select.git
  
  2. Add the javascript and css include tags to your /app/views/layouts/application.html.erb
     (or whatever layout you want it included in)
      
     <%= javascript_include_tag 'calendar_date_select/jquery/jquery-1.3.2.min.js' %>
   <%= javascript_include_tag 'calendar_date_select/jquery/jquery.string.1.0.js' %>
   <%= javascript_include_tag 'calendar_date_select/jquery/jquery.calendardateselect.js' %>
  
     <%= stylesheet_link_tag '/stylesheets/calendar_date_select/jquery.calendardateselect.css' %>
      
  3. Add the setup function to your /public/javascripts/application.js
  
     jQuery(document).ready(function($){
      $("[selector]").datetimeselect();
     });
      
  4. Add elements in your pages with the class or id that matches [selector]
     
     Input Elements will show a Calendar in response to the onClick event.
     <input class="[selector]"> OR <input id="[selector]">
     
     Div and Span Elements will have the calendar placed within them and always show the Calendar.
     <div class="[selector]"> OR <div id="[selector]">
     <span class="[selector]"> OR <span id="[selector]">
     
= Configuration
 
  Coming soon...
     
= TODO:
 
  List to come soon...
      
= Based upon the popular:
 
= 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.