Service Blocks

We would like to generalize the Datalog plugin with block-based programming that will recognize or generate events and then invoke diverse activity based on what happens. The block model provides a "toolbox" of operations subject to assembly constraints promising no syntax errors ever.

The IFTTT (if this then that) service recognizes triggers and actions where both have attributes and triggers can be further qualified with parameters. This appears a proven model. site

We imagine the plugin rendering as a block-based program with a start/stop button similar to Datalog. Double-click would open the larger block editor and toolbox. Ctl-Alt-S would save changes with a Journal update.

The Blockly library adds an editor to your app that represents coding concepts as interlocking blocks. It outputs syntactically correct code in the programming language of your choice. Custom blocks may be created to connect to your own application. site

# Examples

Datalog makes many assumptions as to how it will get data. We imagine Service Blocks offering much more wrangling of data as it is recorded.

Pingdom has retired its free tier of out-of-service alerts. We'd like to replace this with a Service Blocks based pinger that could record and alert on service interruptions.

The Report plugin renders as a count-down to the next scheduled report distribution. Slow triggers might offer a similar warning.