### Eclipse Workspace Patch 1.0
#P views
Index: help/api-handlers.html
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/views/help/api-handlers.html,v
retrieving revision 1.1
diff -u -r1.1 api-handlers.html
--- help/api-handlers.html 26 Jun 2008 22:31:36 -0000 1.1
+++ help/api-handlers.html 30 Jul 2008 14:04:50 -0000
@@ -8,23 +8,23 @@
For the query flow:
-- handler->construct()
+- handler->construct()
- Create the initial handler; at this time it is not yet attached to a view. It is here that you can set basic defaults if needed, but there will be no knowledge of the environment yet.
-- handler->set_definition()
+- handler->set_definition()
- Set the data from hook_views_data() relevant to the handler.
-- handler->init()
+- handler->init()
- Attach the handler to a view, and usually provides the options from the display.
-- handler->pre_query()
+- handler->pre_query()
- Run prior to the query() stage to do early processing.
-- handler->query()
+- handler->query()
- Do the bulk of the work this handler needs to do to add itself to the query.
Fields, being the only handlers concerned with output, also have an extended piece of the flow:
-- handler->pre_render()
+- handler->pre_render()
- Called prior to the actual rendering, this allows handlers to query for extra data; the entire resultset is available here, and this is where items that have "multiple values" per record can do their extra query for all of the records available. There are several examples of this at work in the code.
-- handler->render()
+- handler->render()
- This does the actual work of rendering the field.
@@ -36,13 +36,13 @@
*/
class views_handler_filter_node_type extends views_handler_filter_in_operator {
function get_value_options() {
- if (!isset($this->value_options)) {
- $this->value_title = t('Node type');
+ if (!isset($this->value_options)) {
+ $this->value_title = t('Node type');
$types = node_get_types();
- foreach ($types as $type => $info) {
- $options[$type] = $info->name;
+ foreach ($types as $type => $info) {
+ $options[$type] = $info->name;
}
- $this->value_options = $options;
+ $this->value_options = $options;
}
}
}
Index: help/relationship.html
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/views/help/relationship.html,v
retrieving revision 1.3
diff -u -r1.3 relationship.html
--- help/relationship.html 26 Jun 2008 00:58:29 -0000 1.3
+++ help/relationship.html 30 Jul 2008 14:04:51 -0000
@@ -1,7 +1,7 @@
Relationships allow you to expand the query to include objects other than the base query. This is actually made more difficult to understand by the fact that Views actually includes a few relationships by default, and doesn't tell you they're there. For historical reasons, it would be inconvenient to remove these default relationships.
-The main example of the relationship that is there by default is the node --> user relationship; every node has an author, and if a node is in the query, the user who wrote that node is automatically made available. [Note: the author considers it an error that this relationship is automatic, but by the time it was realized this was in error, it was too late to change it.]
+The main example of the relationship that is there by default is the node --> user relationship; every node has an author, and if a node is in the query, the user who wrote that node is automatically made available. [Note: the author considers it an error that this relationship is automatic, but by the time it was realized this was in error, it was too late to change it.]
A similar relationship that is not automatically made available is for node revisions. Each revision has its own author, which is the user who made the revision. By adding the "Node revision: User" relationship, all of the 'user' fields, sorts, filters and arguments available to a user will now be available for the revision author.
Index: help/view-type.html
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/views/help/view-type.html,v
retrieving revision 1.3
diff -u -r1.3 view-type.html
--- help/view-type.html 29 Apr 2008 00:35:07 -0000 1.3
+++ help/view-type.html 30 Jul 2008 14:04:51 -0000
@@ -16,7 +16,7 @@
- Create a module to store the views.
- Add the function MODULENAME_views_default_views() to this module.
-- Export the view you wish to store in your module in code. Cut and paste that into the abovenamed function. Make sure the last line of the view is: $views[$view->name] = $view;
+- Export the view you wish to store in your module in code. Cut and paste that into the abovenamed function. Make sure the last line of the view is: $views[$view->name] = $view;
- Make sure the last line of the function is return $views;
- After you make any changes, be sure to clear the Views' cache. You may do this from the Tools menu.
Index: help/api-tables.html
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/views/help/api-tables.html,v
retrieving revision 1.2
diff -u -r1.2 api-tables.html
--- help/api-tables.html 26 Jun 2008 00:58:29 -0000 1.2
+++ help/api-tables.html 30 Jul 2008 14:04:51 -0000
@@ -1,13 +1,13 @@
Tables are described to Views via hook_views_data(), which returns an array of table information, keyed by the name of the table. For example, if your module is describing three tables, 'foo', 'bar' and 'baz', your array will look like this:
$data = array(
- 'foo' => array(
+ 'foo' => array(
// ...info here...
),
- 'bar' => array(
+ 'bar' => array(
// ...info here...
),
- 'baz' => array(
+ 'baz' => array(
// ...info here...
),
);
@@ -18,13 +18,13 @@
Each item in the array should be a field in the table, with the exception of a special information section called 'table'. Example:
$data['foo'] = array(
- 'table' => array(
+ 'table' => array(
// ... info about the table, described later ...
),
- 'bar' => array(
+ 'bar' => array(
// ... info about the field named 'bar', i.e, foo.bar,
),
- 'baz' => array(
+ 'baz' => array(
// ... info about the field named 'baz', i.e, foo.baz,
),
);
@@ -57,10 +57,10 @@
// Advertise this table as a possible base table
$data['node']['table']['base'] = array(
- 'field' => 'nid',
- 'title' => t('Node'),
- 'help' => t("Nodes are a Drupal site's primary content."),
- 'weight' => -10,
+ 'field' => 'nid',
+ 'title' => t('Node'),
+ 'help' => t("Nodes are a Drupal site's primary content."),
+ 'weight' => -10,
);
@@ -88,9 +88,9 @@
$data['term_data']['table']['join']['node'] = array(
- 'left_table' => 'term_node',
- 'left_field' => 'tid',
- 'field' => 'tid',
+ 'left_table' => 'term_node',
+ 'left_field' => 'tid',
+ 'field' => 'tid',
);
@@ -98,8 +98,8 @@
$data['term_node']['table']['join']['node'] = array(
- 'left_field' => 'nid',
- 'field' => 'nid',
+ 'left_field' => 'nid',
+ 'field' => 'nid',
);
@@ -143,27 +143,27 @@
$data['node']['nid'] = array(
- 'title' => t('Nid'),
- 'help' => t('The node ID of the node.'), // The help that appears on the UI,
+ 'title' => t('Nid'),
+ 'help' => t('The node ID of the node.'), // The help that appears on the UI,
// Information for displaying the nid
- 'field' => array(
- 'handler' => 'views_handler_field_node',
- 'click sortable' => TRUE,
+ 'field' => array(
+ 'handler' => 'views_handler_field_node',
+ 'click sortable' => TRUE,
),
// Information for accepting a nid as an argument
- 'argument' => array(
- 'handler' => 'views_handler_argument_node_nid',
- 'name field' => 'title', // the field to display in the summary.
- 'numeric' => TRUE,
- 'validate type' => 'nid',
+ 'argument' => array(
+ 'handler' => 'views_handler_argument_node_nid',
+ 'name field' => 'title', // the field to display in the summary.
+ 'numeric' => TRUE,
+ 'validate type' => 'nid',
),
// Information for accepting a nid as a filter
- 'filter' => array(
- 'handler' => 'views_handler_filter_numeric',
+ 'filter' => array(
+ 'handler' => 'views_handler_filter_numeric',
),
// Information for sorting on a nid.
- 'sort' => array(
- 'handler' => 'views_handler_sort',
+ 'sort' => array(
+ 'handler' => 'views_handler_sort',
),
);
@@ -172,10 +172,10 @@
$data['node']['edit_node'] = array(
- 'field' => array(
- 'title' => t('Edit link'),
- 'help' => t('Provide a simple link to edit the node.'),
- 'handler' => 'views_handler_field_node_link_edit',
+ 'field' => array(
+ 'title' => t('Edit link'),
+ 'help' => t('Provide a simple link to edit the node.'),
+ 'handler' => 'views_handler_field_node_link_edit',
),
);
@@ -184,11 +184,11 @@
$data['users']['uid_current'] = array(
- 'real field' => 'uid',
- 'title' => t('Current'),
- 'help' => t('Filter the view to the currently logged in user.'),
- 'filter' => array(
- 'handler' => 'views_handler_filter_user_current',
+ 'real field' => 'uid',
+ 'title' => t('Current'),
+ 'help' => t('Filter the view to the currently logged in user.'),
+ 'filter' => array(
+ 'handler' => 'views_handler_filter_user_current',
),
);
Index: help/using-theme.html
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/views/help/using-theme.html,v
retrieving revision 1.4
diff -u -r1.4 using-theme.html
--- help/using-theme.html 28 Jul 2008 19:10:26 -0000 1.4
+++ help/using-theme.html 30 Jul 2008 14:04:51 -0000
@@ -16,9 +16,9 @@
And it produced this output:
array (
- 'nid' => '97',
- 'title' => 'Scisco Ideo Vicis Feugiat Qui',
- 'name' => 'luwrepuslan',
+ 'nid' => '97',
+ 'title' => 'Scisco Ideo Vicis Feugiat Qui',
+ 'name' => 'luwrepuslan',
)
Index: help/display-block.html
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/views/help/display-block.html,v
retrieving revision 1.3
diff -u -r1.3 display-block.html
--- help/display-block.html 13 Jun 2008 19:06:29 -0000 1.3
+++ help/display-block.html 30 Jul 2008 14:04:51 -0000
@@ -4,7 +4,7 @@
Blocks do not accept arguments from any source; the only way to get arguments to a block is to provide defaults to it, possibly via the PHP Code default setting. A very common scenario is the following:
-if (arg(0) == 'node' && is_numeric(arg(1))) {
+if (arg(0) == 'node' && is_numeric(arg(1))) {
return arg(1);
}