phase2/beat-blocks

#Beat Blocks

A helpful scaffolding for building out configurable blocks that describe themselves.

##Global Build Dependencies

• node/npm - For package management
• grunt - For task management
• browserify - For bundling various src files into a single distribution

##Dependencies

• lodash
• d3
• Handlebars

##Usage <script type="text/javascript" src="../dist/beat-blocks.js"></script> <script type="text/javascript"> var mySimpleWidget = BeatBlocks.widget('image'); mySimpleWidget.render('#widget'); </script>

See the examples folder of this repo for more detailed information.

##Dev tools install

In root directory of the repo...

npm install

##Development

For development, be sure to have grunt watch running during development so that the bundled distribution is built. This also runs a code linter and unit tests on watch.

Other helper grunt commands are

grunt test - runs lint, complexity checks, and automated tests
grunt build - compiles a distribution copy of the library

##Widget structure

Widgets have a number of methods that make up a widget object. Understanding what each of these methods do is helpful in understanding how to create new and unique widgets. It's helpful to examine src/widget-base.js to get a better understanding of the specifics of how widgets behave.

At their core, a widget is a template file and a simple javascript object.

###Helpful methods

• .config() - Widget configuration get/setter Accepts 0, 1 or 2 parameters

  .config() - Returns the configuration of a widget as an object. .config(obj value) - Sets multiple config options, returns the full configuration of the widget as an object. .config(string key) - Returns the configuration of setting defined by the key of string. .config(string key, string|object value) - Sets the configuration for key to the value of value.

• .render(element) - Renders a widget where at a particular DOM element. Element can either be a string (CSS selector) or a DOMElement.

• .compile() - This method handles preparation of any configuration variables before rendering into a template. Override this method in your custom widgets if you want to load any external data into your template, or generate any additional content for your template before rendering.

• .link() - This method handles any event reactions or DOM manipulation that needs to happen after the initial DOM render. Override this method in your custom widgets to define your own js behaviors.

• .template() - The actual rendering method for a widget. By default, widgets use Handlebars.js for templating purposes.

beat-blocks's Issues

Add properties method to widget base

We want components to be able to tell users what kind of information they need to have in their configuration. This should enable us to write generic BeatBlock integrations to provide config to a component.

We should use the JSON-Schema standard as a starting point for how to format this information.

http://json-schema.org/

config .has() method fails if root level item is missing

Make Handlebars/D3 optional

We currently define a handlebars plugin in BeatBlocks that doesn't check to see if handlebars exists or not, so we get an error importing BeatBlocks without also having Handlebars installed.

Declare proper dependencies in bower.json