? views-embedded-help.patch
Index: views.module
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/views/views.module,v
retrieving revision 1.222
diff -u -p -r1.222 views.module
--- views.module	21 Feb 2008 02:32:07 -0000	1.222
+++ views.module	22 Feb 2008 18:04:20 -0000
@@ -75,6 +75,28 @@ function views_theme() {
 }
 
 /**
+ * Implementation of hook_help().
+ */
+
+function views_help($path, $arg) {
+  switch ($path) {
+    case 'admin/help#views':
+      $output = '<p>'. t('The views module, a required component of the <a href="@project-views">Views project</a>, allows administrators and site designers to create, manage, and display lists of content. Essentially a "smart" query builder, the views module constructs and executes database queries and displays the results of those queries in a variety of formats. Each list managed by the views module is known as a view, and the output of a view may be provided in the form of a page, a block, or both page and block. Optional navigation aids, including a system path and menu item, are provided for page-based views. Although a view is most often used to display lists of posts (a <em>Node</em> view type), content revisions (a <em>Node revisions</em> view type) or users (a <em>User</em> view type), other modules may make additional data available to Views through the comprehensive <a href="@views-api">Views API</a>, or may make additional data fields available to <em>Node</em>, <em>Node revisions</em> or <em>User</em> views. A view may be restricted to members of specific user roles.', array('@project-views' => 'http://drupal.org/project/views', '@views-api' => 'http://drupal.org/handbook/modules/views/api')) .'</p>';
+      $output .= '<p>'. t('A view may be provided programmatically or entered through a web-based interface provided by the "Views UI" module, an optional but frequently used component of the Views project. When <a href="@modules">enabled</a>, the Views UI interface provides tools for adding, editing or deleting a view at the <a href="@views-administration">views administration page</a>. The Views UI module also provides an import and export feature (allowing view parameters to be moved between sites, or represented programmatically) and other tools.', array('@modules' => url('admin/build/modules'), '@views-administration' => url('admin/build/views'))) .'</p>'; 
+      $output .= '<p>'. t('When constructing a view, a "building block" design provides power and flexibility, allowing the designer to specify parameters only when needed. While an advanced view may use all of the available parameters and creatively apply view concepts to manage complex and highly interactive applications, a simple content listing may only specify a few options. Important view-building concepts include:') .'</p>';
+      $output .= '<ul>';
+      $output .= '<li>'. t('<em>fields</em>, or the individual pieces of data being displayed. Adding the fields <em>Node: Title</em>, <em>Node: Type</em>, and <em>Node: Post date</em> to a node view, for example, includes the title, content type and creation date in the displayed results.') .'</li>';
+      $output .= '<li>'. t('<em>relationships</em>,') .'</li>';
+      $output .= '<li>'. t('<em>arguments</em>, or additional parameters that dynamically refine the view results, passed as part of the path. Adding an argument of <em>Node: Type</em> to a node view with a path of "content", for example, dynamically filters the displayed items by content type. In this example (shown with Clean URLs enabled), accessing the view through the path "http://www.example.com/content/page" displays all posts of the type "page", the path "http://www.example.com/content/story" displays all posts of the type "story", and "http://www.example.com/content" displays all posts regardless of type.') .'</li>';
+      $output .= '<li>'. t('<em>sort criteria</em>, which determines the order of items displayed in the view results. Adding the sort criteria <em>Node: Post date</em> (in descending order) to a node view, for example, sorts the displayed posts in descending order by creation date.') .'</li>';
+      $output .= '<li>'. t('<em>filters</em>, which limit items displayed in the results. Adding the filter <em>Node: Published</em> (and setting it equal to "Published") to a node view, for example, prevents unpublished items from being displayed.') .'</li>';
+      $output .= '</ul>';
+      $output .= '<p>'. t('For more information, see the online handbook entry for <a href="@handbook-views">Views</a> or the <a href="@project-views">Views project page</a>.', array('@handbook-views' => 'http://drupal.org/handbook/modules/views', '@project-views' => 'http://drupal.org/project/views')) .'</p>';
+      return $output;
+  }
+}
+
+/**
  * Implementation of hook_menu().
  *
  * This probably needs to actually be hook_menu_alter or something.
@@ -930,4 +952,4 @@ function views_theme_functions($hook, $v
   $themes[] = $hook;
 
   return $themes;
-}
\ No newline at end of file
+}