Each bean instance has a corresponding block. Users interact with them in the same way they might use any other block in Drupal. The Bean module does not attempt to interface with the placement of blocks. Bean deals only with the creation of customized, fieldable blocks.
The hardest part about using drupal's javascript features is knowing where to begin: they remained an arcane mystery to me until today. After drinking a bit of whiskey, and studying how core was using Drupal.behavior, I learned it couldn't be simpler. If you don't know how to do this, take a moment:
In brief it integrates Selenium2 to simpletest framework of Drupal. From the beginning it was possible to run test in Firefox that opens pages of the simpletest sandbox. As we are in full control of browser we are able to test javascripts in it.
Automatically download and update your translations fetching them from localize.drupal.org or any other Localization server.
Normally drupal.org inserts version information when a project is packaged. Git repositories do not contain this information. Git Deploy hooks into the Drupal update system and attempts to provide the version of modules and themes checked out of git.
Ubercart2 installations-/Konfigurationsanleitung
