Rationalizing / editing / cleaning up OnClick.yml structure ...

Ideally, one should be able to read onclick.yml and know exactly
what will happen when a certain <a> is clicked. Right now, the
underlying vocabulary is a bit  verbose
Changes related to simplified YAML not working exactly as expected ...

Hence, stashing the changes locally for now so that other issues can
be solved and committted on master

Will come back to this later
Incorporated new form YAML

The new YAML is more intuitive ad therefore easier to edit / modify.
Anyone reading it should be able to figure out exactly what sequence
of actions will result when a certain link is clicked

The aim is to write the least possible HAML and the most possible YAML.
The YAML parser is now smarter and sets some data-* attributes on its own
( such as data-no-touch | data-toggle )
Merge branch 'yaml'

Conflicts:
	app/assets/javascripts/core/trigger.js.coffee