Skip to content
This repository

The server-side sub-project of Exhibit3

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 demos
Octocat-spinner-32 modules
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .project
Octocat-spinner-32 README.markdown
Octocat-spinner-32 backstage
Octocat-spinner-32 backstage.bat
Octocat-spinner-32 butterfly.properties
Octocat-spinner-32 log4j.properties
Octocat-spinner-32 modules.properties
Octocat-spinner-32 pom.xml
README.markdown

Backstage

This is the source for Backstage, originally from the SIMILE SVN repository. We expect to see this satisfy the need for a server-side backend working with Exhibit 3.0.

Usage

You will need a JVM installed with appropriate enviornment settings (JAVA_HOME, etc) along with Maven 2.x+. You will also need Babel as well as SIMILE Butterfly. Butterfly should be installed in a peer directory to Backstage, like:

src/
  backstage/
  butterfly/

Butterfly can be checked out from Google Code repository with SVN. The Google Code version supercedes the SIMILE repository version

Installing Maven dependencies

Run mvn install for Babel to install the dependencies Backstage needs. Babel is currently in the process of transitioning to Maven Central and is not reliably available in other Maven repositories.

Run ant build for Butterfly.

Setting up Backstage

Run mvn package for Backstage to compile its classes to the correct location and copy its Maven dependencies into place within the module. Butterfly is no longer Maven-run software, so its classloader must be able to find classes within the Backstage module.

Working in Eclipse

You can work with Backstage in Eclipse by running mvn eclipse:eclipse in the modules/backstage/ directory, then importing just the module into Eclipse as a project.

JSLint

Backstage also provides a client-side set of scripts that can be checked against JSLint by invoking mvn jslint4java:lint in the modules/backstage directory.

Something went wrong with that request. Please try again.