How Blocks Cooperate

A new block would be implemented as a function that is handed select interpreter state. Blocks can agree to pass application data in fields of their own choosing within that state.

A typical setup would be for one block to collect information, a second block transform that into the desired form, and then a third block distribute the result in some convenient way.

An example of this would be:

NEIGHBORS fed.wiki WALK 10 steps PREVIEW graph

Here NEIGHBORS collects sitemap data from a few sites; WALK takes a short random walk through this data; then PREVIEW creates and opens a ghost page with the walk illustrated with the Graphviz plugin.

Each of these blocks takes an argument to customize its function. When wrapped within the CLICK block the state passed between each block is reported in place with a shift-click. CLICK does this by setting the "debug" state to true.

CLICK NEIGHBORS fed.wiki WALK 10 steps PREVIEW graph

Some blocks will console.log elaborate details when debug is true. Mature blocks will just log that they have run so that new block has lots of clean log space to talk to its developer.

Try this Mech with more neighbors. Mech reaches into its own environment to retrieve sitemaps with no additional network activity.

found.ward.fed.wiki ward.dojo.fed.wiki