Developer tools

This is an example module.

Example implementation of state_machine/state_flow.

This module provides a field for entities that allows users to select what template the field should be displayed in.

This module currently does the following:

After discussing with @dlobo in #civicrm Drupal channel, I start completely rewrite the civicrm Drupal bridge (the Drupal modules in civicrm)

The goals are:

1. Write more "drupalist" code.
2. Using the drupal.org issue queue for faster bugfixing.
3. Split functionality when we are in civicrm section (http://example.com/civicrm/*) or in normal drupal pages.
4. The civicrm is really great, but I understand Drupal developers, why they doesn't like it. I want to create drupallike civicrm by using civi_api.
5. Remove dependency of sites/all/modules directory, first try to put into sites/all/libraries, then using libraries api.
6. Write drupal tests

Usage:

1. Download the civicrm from CiviCRM home page to sites/all/modules directory.
2. Delete the drupal directory from sites/all/modules/civicrm
3. Download this module as a usual drupal module, and enable it.
4. Install CiviCRM.

Notice:

All of this project is completely a plan. Let see, how is this work. There should be some licencing problem, but as I plan, the original code will be full rewritten.

This module provides a Bean (http://drupal.org/project/bean) plugin for the great Twitter Pull module (

Bridge module linking Domain Access and Content Access modules.

[TODO]