Developer

Background

This module creates flatstores for entities. Stores here refers to database tables and flat means these stores contain all of the entity's field data without any joins (see comparison to non relational dbs). Drupal stores field data in separate tables (rightfully so); loaded entities must be JOINed together in SQL; the more joins, the worse the performance and the higher the memory use (see performance section). In short: one entity type, one table. This module is aimed at developers - particularly those creating and exposing large data sets (APIs).

Introduction

The idea behind this module is to create a simple set of tools to make it easy to do integrations with Trello. For now only reading is supported. The module does nothing in itself, but enables developers to more easily do various things like getting boards or cards without understanding the Trello API

Example Code

I've written a small example of how to display a Trello board in Drupal with all the lists, cards and labels attached to the cards. This shows how easy it can be to display something from Trello on a Drupal site.

Enki is like the crazy scientist version of https://www.drupal.org/project/devel_themer . This one wraps theme functions and templates and puts information in comments instead of making them visible. The information includes the name of the theme hook and the name of every variable, followed by a list of (pre)process function that added or changed this variable. A * before the variable name means it was there before (pre)process.

Locate specific panes.

This is a WIP for some object-oriented classes that wrap Drupal Commerce entities such as Order, LineItem and Product. They're designed to be simple and light weight and offer a few benefits:

1. Makes testing your own code that relies on Commerce entities much easier.
2. Simplifies getters/setters rather than using field api and entity_metadata_wrapper functions.
3. Allows you a base to extend if you want to enforce specific actions or rules on the entity.

The purpose of this module is to split out a form into smaller pieces for localization. This module lives on top of form API allowing you(the developer) to break out your form render array into sub blocks to be pieced together within the form hook.

Prefixer is simple module that allows you to set up prefixes for machine names provided by Drupal core and contributed modules (content types, fields, views and so on).

Notice that the module has no affect on any existing elements and can be disabled on production environment.

Introduction

The Feedback Collect module allows site builders to add feedback forms to their sites and gather end user feedback, bug reports or any kind of suggestions. It is highly customizable.

Module to banish modules, themes, and more so they can't be installed and don't even show up in the UI. On cache_clear, banish will disable and uninstall any modules that should have been banished already so you can push new items to banish and your production server will automatically remove them.

Example: Remove PHP Filter module

Say you want to make sure the php module is never turned on. Simply add the following to an enabled modules info file.

banish[module][] = php

Introduces a function called dpm_once() that only runs dpm once from each place it is called.

This code is not mine. I copied it from here:
http://dropbucket.org/node/1478
There is also a patch to be merged to devel here:
https://www.drupal.org/node/2294133

but because I needed the functionality and I wanted to be able to include it in my dev-profiles easily I opted to create this mini-module.