Developer

Developer helper tool for GIT users.
Browser based GUI to administer the GIT hook actions with drush backend.

Drummm helps monitoring Drupal website the way is best for you.

Anyone can create, declare, share and use his own:
- Monitors: SQL query, and metadata describing this result
- Data format: serialized, json, xml, etc.
- Provider: Syslog, Services, etc.
- Consumer: Local file, service client, phone app, newrelic, etc.
- Display through Views: table, charts, etc.

http://drummm.org is coming soon.

This modules submits the Drupal's Module form as a Batch Process.

This is to avoid timeouts when multiple modules are Activated or Deactivated together.

Each module is enabled one after the other, and dependencies are treated like wise.

The module will also check if it is disabling or uninstalling itself and skip the batch creation.

This is a fork of Restful Web Services for the Google Summer of Code 2012 Project Improving RESTful Web Services..
All the development that is done here will be later delivered as patches.

GIT example for http://iteducation.com.ua/training/osnovy-razrabotki-modulei-dlya-drupal...

entity_example from Andy Postnikov
advanced entity example from Yuri Gerasimov

Records all cookies that all users have set when they load a page.

This allows easier auditing of cookies on your websites for conformance with the EU cookie law.

Information appears under admin/reports/cookies

Module to migrate sites built on Big Medium CMS to Drupal.

Important: This module is for developers only, it provides facilities developers can use in custom modules. It does not add anything to a website on its own. Only install it if another module asks for it.

Xu is an evolving set of developer utilities for working with Drupal (like Chaos Tools).

Drupal 7

Xu for Drupal 7 is a PSR-0 compliant library of common functionality. None of the D6 functionality has yet been ported and it is limited and evolving. Ctools is no longer a dependency.

Drupal 6

These are mostly helpful functions which I have found cause to reuse in multiple modules, and are organised into libraries (of functions) and helpers (classes). Individual libraries are documented in the code.

When debugging relatively complicated pages with multiple Contexts set, I've often wondered "What Context is *that* block being enabled by?" Rather than laboriously set the "Debug" Reaction manully on every Context, this simple module modifies every Context that gets loaded and sets the "Debug" reaction automatically.