Developer tools

For now it uses exiftool to fetch exif data from images. But I want to build a plugin structure with providers so multiple sources can be used to fetch exif data.

Drush is a very nice framework for building CLI tools. But it's not a proper ecosystem until it has a todo app.

@Todo is intended to provide developers and administrators with a lightweight task-recording tool that can replace burying @todos in your code. Those can sometimes be useful to inform others of future intent, but are a pain to actually track your own actions.

With new or tiny projects, I often find myself putting high-level notes in an issue tracker somewhere but jotting down more detailed action items in a hard to manage scratch space... @Todo provides cleaner structure and is easily there for me on the command-line when I want to drop a quick thought into the queue.

Again, it is not intended to compete with a real issue tracker. Feature requests oriented at making @Todo scale to more users or more issues will likely be rejected.

Adds CCK display formatter for ImageCache presets that allows for lazy loading of images via the Javascript Image Asynchronous Loading (JAIL) jQuery plugin.

Note: As of 15-01-2014, this module appears to no longer be supported. If you are interested in taking this module over, please reply to the issue.

Xtools helps developing and testing other modules. It offers several dynamic code analysis tools:

• an API to compare data (variable, function return value, ...) to blueprints that define the structure that data should have.
• an API to compare callables (functions, methods, or closures) to signatures that define what parameters those callables should accept and how.
• an API to dynamically expose callables and define their parameters and return values using signatures and blueprints. Xtools comes with a number of definitions for Drupal core and several contributed modules.
• test cases to easily test those callables against their blueprints and signatures. Use it to test your own modules by simply calling XtoolsWebTestCase::XtoolsAssertCallables().
• test cases to test menu router items' and access callbacks' ability to perform access control.

Example use cases

• Test if hook implementations and callbacks return the correct data and are implemented using the correct function signature.
• Validate an entity's data structure using a blueprint.

For a simple example of this module's tests, see Xtools for Drupal core.

The OData Server module exposes entities, like nodes and users, through the OData Producer Library for PHP. Properties and core fields are supported, and the module can be configured to limit the bundles, properties, and fields that are exposed through the server. Hooks are provided for developers to add support for their custom field modules. Most of the read-only conventions of the OData specification are supported.

Sponsored by R2integrated.

Feedback requested !

Overview

This module enables you to have an clear overview per language what the menu entries are. In Drupal all of these links are on the same page and thus it is not clear in which language it is and the menus will grow very big in time aswell.

With this module you will be able to select which menus will be editable by this module. (configuration part)

After you have selected which menus you want to be editable, these menus will be visible separated by language.

This will provide a better overview for customers with bigger menus or for a multi lingual approach.

• at admin/structure/
• for example : admin/structure/main-menu-nl

Features

• Select which menu are being used by this module
• menus per language

Requirements

• Drupal 7
• Internationalization module
• Translated menu's (This is not an module, you must have translated your menu's or selected the option this menu is translatable.)
• Variable module

Keywords:

• Menu by language
• Menu per language
• Menu language