A couple more help files, mostly stubs

css/admin.css

@@ -533,3 +533,9 @@ html.js .views-hidden {
 .views-edit-view .advanced-help-link {
   padding-right: 3px;
 }
+
+#views-ajax-title .advanced-help-link {
+  position: relative;
+  top: 2px;
+  padding-right: 3px;
+}

help/analyze-theme.html

+<!-- $Id$ -->
+<p>You may use any of the following possible theme files to modify individual parts of your view. In total, there are four parts to theming a view.</p>
+<ul>
+  <li> The <strong>display</strong> theme is usually views-view.tpl.php and it largely controls the decorations around a view; where the header, footer, pager, more link, feed icon, etc, will be placed. </li>
+
+  <li> The <strong>style</strong> will control how all of the results of the display are put together. It may be as simple as just displaying all of the rows, or it may be a complex table generator or something in between. </li>
+  
+  <li> The <strong>row</strong> style controls each individual row; not all styles utilize the row style (notably the table), but most others do. 
+  
+  <li> Finally, <strong>field</strong> themes allow you to override the look and even the data of each individual field, if the style uses fields. The actual template the system will use should be hilighted in <strong>bold</strong>.</li>
+</ul>
+
+<p>The link to the left of each type will give you information about the default template used for that type. You may cut and paste this and place it in your theme with the appropriate template, or you may copy the base file from the views/theme directory (or, if provided by a module, from the module's directory). <strong>It is important that you clear the theme registry cache every time you add a new template, or the new template will not be picked up.</strong></p>
+
+<p>Also, this feature will only work properly with Drupal 6.3 and later; prior to Drupal 6.3 <a href="http://drupal.org/node/241570">this patch</a> will be required.</p>

help/menu.html

+<!-- $Id$ -->
+@todo text needed
\ No newline at end of file

help/path.html

+<!-- $Id$ -->
+@todo text needed
\ No newline at end of file

help/views.help.ini

@@ -81,3 +81,12 @@ parent = style
 [style-node-rss]
 title = "Node RSS item row style"
 parent = style
+
+[menu]
+title = "Menu options (page display)"
+
+[path]
+title = "Path options (page display)"
+
+[analyze-theme]
+title = "Theme information"

includes/admin.inc

@@ -1213,6 +1213,12 @@ function views_ui_standard_form_buttons(&$form, &$form_state, $form_id, $name =
   if (isset($form['#title'])) {
     $form_state['title'] = $form['#title'];
   }
+  if (isset($form['#help_topic'])) {
+    $form_state['help_topic'] = $form['#help_topic'];
+  }
+  if (isset($form['#help_module'])) {
+    $form_state['help_module'] = $form['#help_module'];
+  }
   if (isset($form['#url'])) {
     $form_state['url'] = $form['#url'];
   }

includes/ajax.inc

@@ -64,6 +64,10 @@ function views_ajax_form_wrapper($form_id, &$form_state) {
     $object->display .= $output;
 
     $object->title = empty($form_state['title']) ? '' : $form_state['title'];
+    if (!empty($form_state['help_topic'])) {
+      $module = !empty($form_state['help_module']) ? $form_state['help_module'] : 'views';
+      $object->title = theme('advanced_help_topic', $module, $form_state['help_topic']) . $object->title;
+    }
     $object->url = empty($form_state['url']) ? url($_GET['q'], array('absolute' => TRUE)) : $form_state['url'];
     $object->js = empty($form_state['js settings']) ? NULL : $form_state['js settings'];
     if (!empty($form_state['#section'])) {

includes/plugins.inc

@@ -1020,6 +1020,7 @@ class views_plugin_display extends views_plugin {
         break;
       case 'analyze-theme':
         $form['#title'] .= t('Theming information');
+        $form['#help_topic'] = 'analyze-theme';
         $funcs = array();
 
         // Get theme functions for the display. Note that some displays may
@@ -1052,12 +1053,6 @@ class views_plugin_display extends views_plugin {
           }
         }
 
-        $form['markup'] = array(
-          '#prefix' => '<div class="form-item description">',
-          '#suffix' => '</div>',
-          '#value' => '<p>' . t('You may use any of the following possible theme files to modify individual parts of your view. In total, there are four parts to theming a view. The <strong>display</strong> theme is usually views-view.tpl.php and it largely controls the decorations around a view; where the header, footer, pager, more link, feed icon, etc, will be placed. The <strong>style</strong> will control how all of the results of the display are put together. It may be as simple as just displaying all of the rows, or it may be a complex table generator or something in between. The <strong>row</strong> style controls each individual row; not all styles utilize the row style (notably the table), but most others do. Finally, <strong>field</strong> themes allow you to override the look and even the data of each individual field, if the style uses fields. The actual template the system will use should be hilighted in <strong>bold</strong>.') . '</p>',
-        );
-
         $form['important'] = array(
           '#prefix' => '<div class="form-item description">',
           '#suffix' => '</div>',
@@ -1792,6 +1787,7 @@ class views_plugin_display_page extends views_plugin_display {
     switch ($form_state['section']) {
       case 'path':
         $form['#title'] .= t('The menu path or URL of this view');
+        $form['#help_topic'] = 'path';
         $form['path'] = array(
           '#type' => 'textfield',
           '#description' => t('This view will be displayed by visiting this path on your site. You may use "%" in your URL to represent values that will be used for arguments: For example, "node/%/feed".'),
@@ -1801,6 +1797,7 @@ class views_plugin_display_page extends views_plugin_display {
         break;
       case 'menu':
         $form['#title'] .= t('Menu item entry');
+        $form['#help_topic'] = 'menu';
         $form['menu'] = array(
           '#prefix' => '<div class="clear-block">',
           '#suffix' => '</div>',