waterbearlang/waterbear — Issue #117: Hooks
Author: dethe
Created: 2012-01-22 18:27:34+00:00
State: open

Defining points-of-entry for customization (probably using events) is important. Below are some thoughts on how to find the right places in the code for the hooks.

What are the places that have to be touched to introduce a new type?

A new plugin/library?

A new plugin/language?

How to have mutually incompatible libraries (simple vs pro, Raphael vs canvas vs processing)?

Some blocks work best if the can start acting when dropped in a page, or customized (begin preloading an image)

The more these hooks can be separated, the easier to generalize waterbear and make it possible to create powerful languages. I already see places where things like "returns" could pick up most of the block by pattern, only needing exceptions to be spelled out.