start > Software > net.loadbang.shado

net.loadbang.shado

Created by nick. Last edited by nick, 120 days ago. Viewed 1,260 times. #18

[diff] [history] [edit] [rdf]

labels

attachments

shado is an open-source compositing and sprite library for the monome. It is written in Java, but designed to work seamlessly with a lightweight scripting language like Groovy or Python.

We have assembled a number of demonstration programs using Jython under Max/MSP, but the system should work in any Java environment, and the scripting layer is optional.

We have a video of a demo animation sequence built using shado:

YouTube: monome 64 / monome 128
Vimeo: monome 64 / monome 128

Here are copies of the README and the nascent README.MANUAL from the release, which should illustrate how shado works and how to use it.

Installation

The examples are written in Python and hosted in Max/MSP, so our Jython package is a prerequisite for running them. shado needs net.loadbang.lib-1.4 or later - Jython and Groovy used to come bundled with 1.3, so check the versions.

Download this ZIP file: /download/net.loadbang.shado-1.0-20080723.zip. This archive contains instructions, plus the required JAR files, examples, javadocs and sources. The javadocs are also available online here.

Releases

* (1.0) 2008-07-23:

Added a back-port of the "simple" demo patcher to Max 4.

* 1.0, 2008-07-20:

Non-beta release, with a last-minute API modification: Frame.add() no longer returns stamps; use the actual renderable in Frame.top() etc.

Synchronization of methods (in Frame, predominantly) for thread-safety.

A revamp and tidy-up of the demo programs (and a change of prefix to "/shado").

* 0.9b3, 2008-07-17:

Machinery for handling and routing button presses.

* 0.9b2, 2008-07-13:

Addition of ViewPort renderables, for cropping and providing view ports on other renderables.

A minor fix to the Tapestry Python demo: now (correctly) loading config info from a Python module (tapestry/shared/config.py).

Also, a typo fix to the example Python code in the manual.

* 0.9b1, 2008-06-27:

Initial beta release.

Release Numbering

All releases have two parts to their version: an actual version number, and a date. The version number changes if the core Java code is changed; the date changes if the Java code changes, or if there are any changes to example code or 3rd-party libraries.