Simple git workflow for creating core patches. This page documents a high-level overview of the current best practice recommendations for contributing change requests, in the form of a patch file, to projects (e.g., modules, themes, Drupal core, etc) hosted on Drupal.org using Git. For a more advanced workflow with Git, please refer to the Advanced patch contributor guide.
Drush issue queue commands makes it easier and faster to create and work with patches. Note 1: If you're unfamiliar with patching Drupal, please read the Getting Involved section on Patches. Note 2: If you choose to create patches with a tool other than Git, be sure to produce a -p1 patch; the old -p0 format was phased out in 2011 There is a short video on Applying and Creating Patches with Git that covers much of this material as well. General patch guidelines Keeping things organized To help reviewers understand the scope of changes, separate each change type into its own patch. Line endings and directory separators Quick and simple patch To see if it worked: Notes e.g. Drupal 6.15 for Zymic | kemralight.com. DrupalCon DC - Business Analytics in Drupal with Views | computerminds. One of the interesting sessions that I attended at DrupalCon DC was one entitled: Business Analytics in Drupal with Views.
In it, the presenters showcased two of their modules. One was a charts display plugin for views, and one was a 'group by' views field. Views charts This was a simple module to take the output of a views query and pump it into a flash charting framework. Being able to display the output of your views with charts is really nothing new, and the presenters admitted to duplicating existing modules.
Hopefully a module will emerge from the mess that will be simple enough, yet flexible enough to take the lead so that we can standardise on that one. There's no sense in having lots of module that all run across the same problems but have slightly different limitations, I'd much rather see a standard views output plugin that can support different charting frameworks for the actual rendering. The 'meat' of the session was much more interesting... Views Group By. Drupal 7 Tutorials | New Features.
Using the theme layer (Drupal 6.x) See also: Theme handbook (D6) Modules in Drupal have the capability to allow presentation to be overridden for use on individual sites; this capability is called theming. In order for the theme layer to be usable, a module must be written to take advantage of it. To do this, logic must be separated as much as possible from presentation. To accomplish this, modules do as much of the work on the data as possible, and hand that data off to the presentation layer. Modules then provide default implementations that provide the basic presentation and serve as a basis for themes that wish to provide an alternate presentation. This is handled through the theme() function.
Ideally, your module won't produce a single line of HTML output that is not in a theme implementation. Registering theme hooks In order to utilize a theme hook, your module first has to register that this exists. <? This registration tells us that a theme hook named forums is implemented. Implementing default templates. Developing for Drupal. Burt Lo's videos.