Now all modules are in core modules folder

modules/calendar/help/attachments.html

@@ -0,0 +1 @@
+<p>Views 2 lets you combine a number of 'displays' together in one view, including, potentially, more than one page display. Each page display can be a regular page display, with its own url, or an 'attachment' to another display. Attachments are basically one or more views that all appear at the same url of the page they are attached to, one after the other. So the calendar now creates one display that creates the back/next navigation, and attaches to it a year, month, week, or day display with the calendar for the right period.</p>

modules/calendar/help/calendar.help.ini

@@ -0,0 +1,43 @@
+; $Id: calendar.help.ini,v 1.1.2.4 2008/10/28 11:46:19 karens Exp $
+
+[advanced help settings]
+name = Calendar
+index name = "Calendar"
+
+[overview]
+title = Overview
+
+[getting-started]
+title = Getting started
+parent = overview
+weight = 1
+
+[settings]
+title = Settings
+parent = overview
+weight = 2
+
+[attachments]
+title = Attachments
+parent = overview
+weight = 3
+
+[embedding]
+title = Embedding views
+parent = overview
+weight = 10
+
+[ical]
+title = iCal
+parent = overview
+weight = 5
+
+[ical-export]
+title = iCal Export
+parent = ical
+weight = 1
+
+[ical-import]
+title = iCal Import
+parent = ical
+weight = 2

modules/calendar/help/embedding.html

@@ -0,0 +1,15 @@
+<h3>Embedding Views</h3>
+<p>Embed a date browser or calendar view anywhere using the format: <pre>date_embed_view($view_name, $display_name, $settings, $args)</pre> 
+Settings are used to override some values of the view.</p>
+<p>The primary setting that is useful here is a setting for 'block_identifier'. The view's block_identifier is used to control individual instances of regular and embedded views that contain date navigation so that they move separately or together. All views that use the same identifier will move together. 
+All views that use different identifiers will move independently. The identifier will show up in the url as a querystring, like node/275?mini=calendar/2008-10. 
+Page views use no block identifier, the normal identifier of the block view is 'mini'.</p>
+<h3>Examples:</h3>
+<dl>
+<dt>&lt;?php print date_embed_view('calendar', 'calendar_1'); ?&gt;</dt>
+<dd>This will embed the default page view of the calendar, using the regular calendar defaults.</dd>
+<dt>&lt;?php print date_embed_view('calendar', 'calendar_1', array('block_identifer' => 'embedded'), array('2008-W45')); ?&gt;</dt>
+<dd>This will embed the page view of the calendar that will use 'embedded' as an identifier, set to show the week view for week 45 of 2008.</dd>
+<dt>&lt;?php print date_embed_view('calendar', 'calendar_block_1', array('block_identifier' => 'mini'), array('2008-07')); ?&gt;</dt>
+<dd>This will embed the block view of the calendar that will use 'mini' as an identifier, set to show the month view for July 2008.</dd>
+</dl>

modules/calendar/help/getting-started.html

@@ -0,0 +1,22 @@
+
+<ol>
+<li>Create a new calendar by enabling the default calendar view and changing it to use whatever date you want in your calendar. You can create multiple calendars by cloning the default calendar view as many times as necessary.</li>
+
+<li>The calendar uses the <a href="topic:date_api/date-argument">Generic Date argument</a>. This argument has an option to select one or more Views date fields to filter on, automatically adds them to the view, and then filters the view by the value of the selected field(s). This argument can be used on any view, not just calendar views.</li>
+
+<li> Unlike previous versions of the Calendar module, there is just a single argument instead of year, month, and day arguments. The argument value will be YYYY-MM-DD for a day, YYYY-MM for a month, YYYY for a year, and YYYY-W99 for a week. There is a default option to set the argument to the current date when the argument is empty.</li>
+
+<li>A calendar display creates calendar navigation and links to multiple displays for the year, month, day, or week views. The actual displays are created by attaching calendar views that use whatever styles are desired for those pages.</li>
+
+<li> Calendar views are attachments <a href="#note1">(note 1)</a> to create the year, month, day, and week displays. They can be set to use any style, either a calendar style or any other Views style, like teasers or lists. They can each have their own fields and formatting. They must be attached to the main calendar page or to a calendar block.</li>
+
+<li>If you don't want to have a link to a week display, just remove the week display from the view. Ditto for any other displays you don't want to use. The links will automatically disappear for any displays that are not defined in the view.</li>
+
+<li>A calendar block will create a calendar block for the view results. This block requires the calendar argument to do its work, and uses one of the year, month, day, or week calendar view attachments created above. </li>
+
+<li>Earlier versions required that you add the date field to the 'Fields' section of the view, but this version does not require that. Add the field to the view if you want it displayed in the results, otherwise you can leave it out. The Calendar no longer over-writes normal formatting for that field, it will be displayed however you set it up in the view.</li>
+
+<li>There are templates for the top of the calendar (the links and navigation), the year, month, day, and week displays, and the individual month, week, and day nodes, so you can easily style them.</li>
+
+</ol>
+

modules/calendar/help/ical-export.html

@@ -0,0 +1,2 @@
+<p>If the Calendar iCal module is enabled, the default Calendar view will include an iCal display that you can use to create iCal exports of your calendar.</p>
+<p>To use the iCal export, look for the iCal display in the calendar. The default iCal feed uses a Date filter set to show events greater to or equal to 'now'. Find the <a href="topic:date_api/date-filter">date filter</a> on the iCal display and change it to use the date(s) used in the calendar. Then attach the iCal feed to the Calendar Page and/or the Calendar Block.</p>

modules/calendar/help/ical-import.html

@@ -0,0 +1,4 @@
+<p>To import nodes from an iCal feed, follow the <a href="topic:date_api/ical-import">iCal Import</a> instructions.</p>
+<p>After importing, the imported nodes now exist as regular date fields that can be added to your calendar. </p><p><img src="&path&images/ical_import.png"></p>
+
+</ol>

modules/calendar/help/ical.html

@@ -0,0 +1 @@
+The Calendar module can take advantage of the iCal standard to either export or import ical feeds.

modules/calendar/help/overview.html

@@ -0,0 +1,3 @@
+<h3>Calendar 2.0 for Drupal 6</h3>
+Calendar 2.0 for Drupal 6 entailed a complete rewrite in order work with Views 2. There are a lot of changes from earlier versions, so I strongly suggest you start with the default calendar view provided and add and edit it to get the results you want.
+

modules/calendar/help/settings.html

@@ -0,0 +1,7 @@
+<p>Calendar settings are now all done in the view instead of on a separate settings page in the administration area.</p>
+
+<p>See the screenshots below for the place to edit the legend colors.</p>
+
+<p><img src="path:images/calendar_colors.jpg"></p>
+
+<p><img src="path:images/calendar_colors2.jpg"></p>