Commit 9a9f74a7 authored by The Great Git Migration's avatar The Great Git Migration Committed by Drupal Git User (LDAP)

Stripping CVS keywords

parent b6eb09b7
/* $Id$ */
div.export-container {
width: 48%;
......
; $Id$
name = Bulk Export
description = Performs bulk exporting of data objects known about by Chaos tools.
core = 6.x
......
# $Id$
#
# LANGUAGE translation of Drupal (bulk_export)
# Copyright YEAR NAME <EMAIL@ADDRESS>
......
/* $Id$ */
.ctools-collapsible-container .ctools-toggle {
float: left;
......
/* $Id$ */
.ctools-context-holder .ctools-context-title {
float: left;
width: 49%;
......
/* $Id$ */
.ctools-locked {
color: red;
border: 1px solid red;
......
/* $Id$ */
html.js div.ctools-dropdown div.ctools-dropdown-container {
z-index: 1001;
display: none;
......
/* $Id$ */
body form#ctools-export-ui-list-form {
margin: 0 0 20px 0;
}
......
/* $Id$ */
div.ctools-modal-content {
background: #fff;
color: #000;
......
/* $Id$ */
/* Farbtastic placement */
.color-form {
......
/* $Id$ */
.wizard-trail {
font-size: 120%;
......
<?php
// $Id$
/**
* @file
......
; $Id$
name = Chaos tools
description = A library of helpful tools by Merlin of Chaos.
core = 6.x
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file
......
; $Id$
name = Custom rulesets
description = Create custom, exportable, reusable access rulesets for applications like Panels.
core = 6.x
......
<?php
// $Id$
/**
* Schema for customizable access rulesets.
......
<?php
// $Id$
$plugin = array(
'schema' => 'ctools_access_ruleset',
......
<?php
// $Id$
class ctools_access_ruleset_ui extends ctools_export_ui {
......
; $Id$
name = Chaos Tools (CTools) AJAX Example
description = Shows how to use the power of Chaos AJAX.
package = Chaos tool suite
......
; $Id$
name = Custom content panes
description = Create custom, exportable, reusable content panes for applications like Panels.
core = 6.x
......
<?php
// $Id$
/**
* Schema for CTools custom content.
......
<?php
// $Id$
$plugin = array(
'schema' => 'ctools_custom_content',
......
<?php
// $Id$
class ctools_custom_content_ui extends ctools_export_ui {
......
// $Id$
The CTools Plugin Example is an example for developers of how to CTools
access, argument, content type, context, and relationship plugins.
......
<!-- $Id$ -->
The Chaos Tool Suite is a series of tools for developers to make code that I've found to be very useful to Views and Panels more readily available. Certain methods of doing things, particularly with AJAX, exportable objects, and a plugin system are proving to be ideas that are useful outside of just Views and Panels. This module does not offer much directly ot the end user, but instead creates a library for other modules to use. If you are an end user and some module asked you to install the CTools suite, then this is far as you really need to go. If you're a developer and are interested in these tools, read on!
<h3>Tools provided by CTools</h3>
......
<!-- $Id$ -->
access plugins allow context based access control to pages.
......
<!-- $Id$ -->
Arguments create a context from external input, which is assumed to be a
string as though it came from a URL element.
......
<!-- $Id$ -->
<p>The CTools pluggable content system provides various pieces of
content as discrete bits of data that can be added to other
applications, such as Panels or Dashboard via the UI. Whatever the
......
<!-- $Id$ -->
Context plugin data:
......
<!-- $Id$ -->
'title' => The title to display.
'description' => Description to display.
......
; $Id$
[advanced help settings]
line break = TRUE
......
<!-- $Id$ -->
Most user interfaces for exportables are very similar, so CTools includes a tool to provide the framework for the most common UI. This tool is a plugin of the 'export_ui' type. In order to create a UI for your exportable object with this tool, you first need to ensure that your module supports the plugin:
<pre>
......
<!-- $Id$ -->
Exportable objects are objects that can live either in the database or in code, or in both. If they live in both, then the object in code is considered to be "overridden", meaning that the version in code is ignored in favor of the version in the database.
The main benefit to this is that you can move objects that are intended to be structure or feature-related into code, thus removing them entirely from the database. This is a very important part of the deployment path, since in an ideal world, the database is primarily user generated content, whereas site structure and site features should be in code. However, many many features in Drupal rely on objects being in the database and provide UIs to create them.
......
<!-- $Id$ -->
CTools' form tool is a replacement for drupal_get_form() that includes some additional functionality:
<ul>
<li> It takes $form_state as an argument, which is accepted as a reference; meaning when the form is complete, you can examine the $form_state to see what the form did.</li>
......
<!-- $Id$ -->
CTools provides a simple modal that can be used as a popup to place forms. It differs from the normal modal frameworks in that it does not do its work via an iframe. This is both an advantage and a disadvantage. The iframe simply renders normal pages in a sub-browser and they can do their thing. That makes it much easier to put arbitrary pages and forms in a modal. However, the iframe is not very good at actually communicating changes to the main page, so you cannot open the modal, have it do some work, and then modify the page.
<h3>Invoking the modal</h3>
......
<!-- $Id$ -->
The CTools Object Cache is a specialized cache for storing data that is non-volatile. This differs from the standard Drupal cache mechanism, which is volatile, meaning that the data can be cleared at any time and it is expected that any cached data can easily be reconstructed. In contrast, data stored in this cache is not expected to be reconstructable. It is primarily used for storing user input which is retrieved in stages, allowing for more complex user interface interactions.
The object cache consists of 3 normal functions for cache maintenance, and 2 additional functions to facilitate locking.
......
<!-- $Id$ -->
APIs are a form of plugins that are tightly associated with a module. Instead of a module providing any number of plugins, each module provides only one file for an API and this file can contain hooks that the module should invoke.
Modules support this API by implementing hook_ctools_plugin_api($module, $api). If they support the API, they return a packet of data:
......
<!-- $Id$ -->
There are two primary pieces to using plugins. The first is getting the data, and the second is using the data.
<h3>Getting the data</h3>
......
<!-- $Id$ -->
To implement plugins, you need to implement a single hook in your module to tell the system where your plugins live, and then you need to implement one or more .inc files that contain the plugin data.
<h3>Telling it where your plugins live</h3>
......
<!-- $Id$ -->
The plugins tool allows a module to allow <b>other</b> modules (and themes!) to provide plugins which provide some kind of functionality or some kind of task. For example, in Panels there are several types of plugins: Content types (which are like blocks), layouts (which are page layouts) and styles (which can be used to style a panel). Each plugin is represented by a .inc file, and the functionality they offer can differ wildly.
A module which uses plugins can implement a hook describing the plugin (which is not necessary, as defaults will be filled in) and then calls a ctools function which loads either all the known plugins (used for listing/choosing) or loads a specific plugin (used when its known which plugin is needed). From the perspective of the plugin system, a plugin is a packet of data, usually some printable info and a list of callbacks. It is up to the module implementing plugins to determine what that info means and what the callbacks do.
......
<!-- $Id$ -->
Form wizards, or multi-step forms, are a process by which the user goes through or can use an arbitrary number of different forms to create a single object or perform a single task. Traditionally the multi-step form is difficult in Drupal because there is no easy place to put data in between forms. No longer! The form wizard tool allows a single entry point to easily set up a wizard of multiple forms, provide callbacks to handle data storage and updates between forms and when forms are completed. This tool pairs well with the <a href="&topic:ctools/object-cache&">object cache</a> tool for storage.
<h3>The form info array</h3>
......
<?php
// $Id$
// Set this so we can tell that the file has been included at some point.
define('CTOOLS_AJAX_INCLUDED', 1);
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file includes/common-context.inc
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file
......
<?php
/* $Id$ */
/*
* @file
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* Delegated implementation of hook_menu().
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* Fetch metadata on a specific page_wizard plugin.
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file
* Create customized CSS and images from palettes created by user input.
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file
......
<?php
// $Id$
/**
* @file
......
// $Id$
/**
* @file
*
......
// $Id$
/**
* To make a form auto submit, all you have to do is 3 things:
......
// $Id$
/**
* @file
* Javascript required for a simple collapsible div.
......
// $Id$
/**
* @file
*
......
// $Id$
/**
* @file
* Implement a simple, clickable dropdown menu.
......
// $Id$
(function($) {
Drupal.behaviors.CToolsJumpMenu = function(context) {
......
// $Id$
/**
* @file
*
......
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.