Developer tools

Google Chart Tools API is a tool for developers to facilitate the use of Google Chart Tools and the Google Visualization API within the context of a Drupal site. It provides PHP and Javascript wrappers for all features of the Visualization API, and is built to reduce the common limitations of using a wrapper class.

Note: the following is only a brief summary of available classes and methods. In truth, the API is much larger than this as it aims to integrate as many features of the Visualization API as possible. Please see the module code for more information.

Creating a chart

Create a chart using new GoogleChartsChartWrapper([array $options]).

$chart_wrapper = new GoogleChartsChartWrapper(array(
  // Note that chart type must match a chart class available
  // in the google.visualization object.
  'chartType' => 'BarChart',
  'chartName' => 'bar_1',
  'containerId' => 'bar-1',
  'options' => array(
    'chartArea' => array(
      'width' => 600,
      'height' => 600,
    ),
  ),
));

Here's the Javascript API equivalent of the preceeding:

var chart_wrapper = new Drupal.GoogleCharts.Chart('BarChart', 'bar-1', {chartArea: {width: 600, height: 600}});

Drupal's standard installation profile, as a module, so that other modules' installs can depend on it.

Does site configuration for a standard site installation.

This module allows you to put any relative path you'd like for a menu entry, even if the path doesn't exist on your site.

You might need this module for two reasons.

1) You either need to create menu items before the pages/paths are created. Helpful when you are building out new sites for which you haven't actually created the secondary pages yet, or if you want your menu to point to some path that will actually be redirected somewhere else (for which you've already set up a redirect).

This actually isn't why this module was created, but it will work for this.

2) You have a distributed system, with some paths being on one (non-Drupal, or different Drupal install) server, and the other on your current Drupal system. It's assumed that you have some sort of path redirection mechanism in place such as Varnish, nginx or The Big IP to redirect your request to the proper path. But you need to serve your menu from Drupal.

Why not just put an absolute path, you ask? When you put absolute paths, not only does it make it a pain for moving your Drupal site to other environments - but it also doesn't keep the proper base url when your site is serving up translated content. Ideally, http://example.com/your_sneaky_path would change to http://example.co.uk/your_sneaky_path when you changed to UK English (as an example).

A developer module to make form creation easier and eliminate repetitive coding.

Example:

This module displays the world clock time in analog format.As compared to other modules,this module give the users to decide their own timezones to be displayed.So the user's choices (with referenc

Real Estate module will be new project.