Neatline 2.0 alpha1 Installation

Welcome to Neatline 2.0! In the new version, we've split apart the functionality that was bundled together in the first release of Neatline into three separate plugins: Neatline, which houses the core content management system and map-making toolkit; NeatlineSimile, which adds the SIMILE Timeline widget; and NeatlineWaypoints, which adds a sortable list of waypoints.

This new architecture makes it easier to exactly the combination of features needed for a project, and it also makes it possible for developers to implement custom functionality for specific projects.

To get started:

1. Download the .zip archives for the three plugins.
2. Unpack the archives, and move the three folders into the /plugins directory of your Omeka 2.x installation.
3. In the Omeka admin, go to the Plugins tab. You should see listings for the three new plugins.
4. Install Neatline first, then NeatlineSimile and NeatlineWaypoints (which require Neatline to be installed).
5. Once the installation is complete, click on the Neatline tab in the vertical navigation on the left of the screen.
6. Get started with a new exhibit by clicking the green Create an Exhibit button.

Important: Depending on your server environment, you may have to set the PHP path for background processes in the Omeka config.ini file. This is usually unnecessary, but if your Omeka installation is using something other than the default installation of PHP on your system, you'll need to set the path directly (for example, this is the case if you're running Omeka locally in MAMP).

1. Open the application/config/config.ini file in your Omeka installation.
2. Scroll down to the background.php.path entry. Enter in the location of the PHP executable that's being used to run Omeka. For example, if you're using MAMP, this would look like:

background.php.path = "/Applications/MAMP/bin/php/php5.4.4/bin/php"

Equally Important: Let us know what you think! We're going to be pushing out a series of alpha releases over the course of the next couple weeks in pretty rapid succession, and we're really keen to get feedback about the new features before cutting off a stable 2.0 release. If you find a bug, or think of a feature that you'd like to see included, be sure to file a report on the issue tracker.