Panels Extras

Component type

module

Maintenance status

Development status

Downloads

11094

Component created

Component changed

What is Panels Extras?

Panels Extras is a collection of plugins that extends functionality to the Panels module.

Does it do x?

We are actively maintaining Panels Extras to provide extended functionality for the Panels module. Please add plugin requests to the issue queue.

What's inside?

Currently Panels Extras includes the following plugins:

Form Child Theme

Component type

module

Categories

Maintenance status

Development status

Downloads

1770

Component created

Component changed

Form Child Theme is a helper module that allows you to theme the expanded elements of the checkboxes and radios elements within forms simply by adding '#child_theme' as a variable when declaring the element within a form.

For example:

Wysiwyg Fields

Component type

module

Maintenance status

Development status

Downloads

16009

Component created

Component changed

Wysiwyg Fields is an Inline field management system, a module that bridges the gap between Drupal fields and CKEditor, giving the power of Drupal's field system via the simple usability of a CKEditor dialog.

What that means is that Wysiwyg Fields allows for any Drupal field to be embedded directly into CKEditor and behave as a native CKEditor plugin, removing unnecessary clutter from your Drupal entity forms.

 

Body wrap filter

Component type

module

Maintenance status

Development status

Downloads

1091

Component created

Component changed

Introduction

Body wrap filter is a small theme-helper module which provides an input filter to wrap the contents of the node's body field in a div.

Sometimes, when I'm working with custom content types that may have many additional fields besides the title and body content, it can be tricky to style the content that was added to the body field. It can be done using a theme template (.tpl.php) and writing each field separately, but this can be tedious when a simple div wrapper around the body field would suffice.

An input filter seems like a neat way to do this.

The JIT

Component type

module

Maintenance status

Development status

Downloads

3106

Component created

Component changed

The JIT (Javascript InfoVis Toolkit) module provides integration with the Javascript InfoVis Toolkit (http://thejit.org) and Drupal. The JIT is a javascript information visualization library that enables interactive visualizations of data using only html, css and javascript.

7.x

The 7.x version is useful for site builder when installing graphapi which provides views integration.

See the screenshots which are from the 7.x version

DropIn

Component type

module

Maintenance status

Development status

Downloads

1118

Component created

Component changed

The DropIn module allows site developers/administrators to add path based CSS and JS files to their site.

Example
When a visitor requests www.example.com/news/articles/issue-1, the module will look for the next css files in the theme directory:

news.css - styles all pages under news/
news.articles.css - styles all pages under news/articles/
news.articles.issue-1.css - only styles the page issue-1

Node CSS

Component type

module

Maintenance status

Development status

Component created

Component changed

Node CSS uses node fields to populate a CSS template file. CSS for all nodes can either be aggregated into a single file or generated per node. In both modes, the CSS files are added using drupal_add_css() so it complies with full Drupal aggregation and compression. If aggregation is turned on in Node CSS it is recommended to make the CSS node specific via a body node class because the same CSS file is loaded for multiple nodes. Many themes output a node specific class by default.