class views_plugin_node_fullcalendar in FullCalendar 7
Same name and namespace in other branches
- 6 views_plugin_node_fullcalendar.inc \views_plugin_node_fullcalendar
Plugin which performs a node_view on the resulting object.
Most of the code on this object is in the theme function.
Hierarchy
- class \views_object
- class \views_plugin
- class \views_plugin_row
- class \views_plugin
Expanded class hierarchy of views_plugin_node_fullcalendar
1 string reference to 'views_plugin_node_fullcalendar'
- fullcalendar_views_plugins in ./
fullcalendar.views.inc - Implements hook_views_plugins().
File
- ./
views_plugin_node_fullcalendar.inc, line 13 - Contains the node view row style plugin.
View source
class views_plugin_node_fullcalendar extends views_plugin_row {
// Basic properties that let the row style follow relationships.
var $base_table = 'node';
var $base_field = 'nid';
function option_definition() {
$options = parent::option_definition();
$options['fullcalendar_url_field'] = array(
'default' => '',
);
$options['fullcalendar_date_fields'] = array(
'default' => '',
);
$options['fullcalendar_title_field'] = array(
'default' => '',
);
return $options;
}
function options_form(&$form, &$form_state) {
parent::options_form($form, $form_state);
$form['fullcalendar_date_fields'] = array(
'#type' => 'textarea',
'#title' => t('Date Fields'),
'#default_value' => $this->options['fullcalendar_date_fields'],
'#description' => t('Normally this plugin uses the first node field that is either a date or a datetime field type. However, if you wish to override this behavior, please enter the names of the fields to use instead. For example "field_scheduled_for". Enter one per line. They will be searched in the order listed. Enter "created" or "changed" to use the respective node timestamps.'),
);
$form['fullcalendar_title_field'] = array(
'#type' => 'textfield',
'#title' => t('Title Field'),
'#default_value' => $this->options['fullcalendar_title_field'],
'#description' => t('The title of the event to be displayed. If blank, the node title will be used. For example: "field_event_title".'),
);
$form['fullcalendar_url_field'] = array(
'#type' => 'textfield',
'#title' => t('URL Field'),
'#default_value' => $this->options['fullcalendar_url_field'],
'#description' => t('If the calendar items should not link directly to the node, enter the name of the cck field to use for the url instead. For example: "field_url".'),
);
}
function render($row) {
return theme($this
->theme_functions(), array(
'view' => $this->view,
'options' => $this->options,
'row' => $row,
'field_alias' => $this->field_alias,
));
}
}
Members
Name | Modifiers | Type | Description | Overrides |
---|---|---|---|---|
views_object:: |
public | property | Handler's definition. | |
views_object:: |
public | property | Except for displays, options for the object will be held here. | 1 |
views_object:: |
function | Collect this handler's option definition and alter them, ready for use. | ||
views_object:: |
public | function | Views handlers use a special construct function. | 4 |
views_object:: |
public | function | Destructor. | 2 |
views_object:: |
public | function | 1 | |
views_object:: |
public | function | ||
views_object:: |
public | function | Always exports the option, regardless of the default value. | |
views_object:: |
public | function | Set default options on this object. | 1 |
views_object:: |
public | function | Set default options. | |
views_object:: |
public | function | Let the handler know what its full definition is. | |
views_object:: |
public | function | Unpack options over our existing defaults, drilling down into arrays so that defaults don't get totally blown away. | |
views_object:: |
public | function | Unpack a single option definition. | |
views_object:: |
public | function | Unpacks each handler to store translatable texts. | |
views_object:: |
public | function | ||
views_plugin:: |
public | property | The current used views display. | |
views_plugin:: |
public | property | The plugin name of this plugin, for example table or full. | |
views_plugin:: |
public | property | The plugin type of this plugin, for example style or query. | |
views_plugin:: |
public | property |
The top object of a view. Overrides views_object:: |
1 |
views_plugin:: |
public | function | Provide a list of additional theme functions for the theme info page. | |
views_plugin:: |
public | function | Return the human readable name of the display. | |
views_plugin:: |
public | function | Returns the summary of the settings in the display. | 8 |
views_plugin:: |
public | function | Provide a full list of possible theme templates used by this style. | |
views_plugin:: |
public | function | Validate that the plugin is correct and can be saved. | 3 |
views_plugin_node_fullcalendar:: |
property | |||
views_plugin_node_fullcalendar:: |
property | |||
views_plugin_node_fullcalendar:: |
function |
Provide a form for setting options. Overrides views_plugin_row:: |
||
views_plugin_node_fullcalendar:: |
function |
Information about options for all kinds of purposes will be held here. Overrides views_plugin_row:: |
||
views_plugin_node_fullcalendar:: |
function |
Render a row object. This usually passes through to a theme template
of some form, but not always. Overrides views_plugin_row:: |
||
views_plugin_row:: |
public | function | 2 | |
views_plugin_row:: |
public | function |
Perform any necessary changes to the form values prior to storage.
There is no need for this function to actually store the data. Overrides views_plugin:: |
1 |
views_plugin_row:: |
public | function |
Validate the options form. Overrides views_plugin:: |
|
views_plugin_row:: |
public | function | Allow the style to do stuff before each row is rendered. | 5 |
views_plugin_row:: |
public | function |
Add anything to the query that we might need to. Overrides views_plugin:: |
|
views_plugin_row:: |
public | function |