Developers : Requirements

To be able to develop on the LunaSuite code you will need to have a MacOS based machine (MacOS 7.6, 8.0 and 8.1 have been tested, MacOS emulation on PC's has been reported to work also). This is because the build process for the LunaSuite is AppleScripted, and parts of the LunaSuite have been written in C++ which can only be compiled with the Newton C Tools.

Besides the above, you will also need a bunch of software, some of which is commercial -- Sorry 'bout that. Most of the software is required by the build process, so one might be able to do without if you don't need to create entire builds. The following software is required:

MacCVS:

Since the LunaSuite code can only be obtained through the CVS repository, you will need a cvs client for the Mac. The MacCVS client supports everything you'll need. Get the latest beta version because it has some features that you'll need to check out and work on the code. More about checking out the code later...

The Newton Toolkit and NCT:

The be able to build and develop the code you will need the Newton Toolkit. To compile the C++ parts of the code you'll also need the Newton C++ Tools and MPW (included with the NCT as far as I know)

Prefab Player: (build process only)

The automated build process (the AppleScript's) use Prefab's excellent Player to place mouse clicks at the right places to automate everything. This product is commercial, but there's a 30-day evaluation period. We used this product in order to automate NTK and all the other tools that don't have an AppleScript interface.

Eudora Pro: (build process only)

Eudora Pro is required by the build process for error reporting. At some point in time we had a server spitting out snapshots of the LunaSuite every night. The package build scripts use Eudora to send reports about the build. If a build is succesfull you won't need it.

Stuffit Deluxe: (build and backup process only)

Used by the package build scripts to spit out compressed versions of the builds. I think you really need the commercial version. Dropstuff will probably not suffice since I don't think it supports an AppleScript interface. The backup scripts also use Stuffit to compress archives.

Anarchie: (build and backup process only)

After building or backing up, the scripts ftp the results to a server. Anarchie is used for this. It is shareware but well worth it.

Scriptable Text Editor: (build process only)

To edit files, the build scripts use the Scriptable Text Editor. I don't think it comes with AppleScript, but the thing is probably available from Apple's web site.

Applescript Extensions: (build and backup process only)

You need various AppleScript extensions. I can't remember which ones exactly, but here's an archive of my AppleScript Extensions folder. Please select the ones you don't have and put them into your AppleScript Extensions folder.

MacPerl:

Used for constructing parse tables for the HTML parser and for the character set coders. The HTML parser uses tables that are being generated from a customized HTML 3.2 DTD by MacPerl. The character (en/de)coders use tables generated from the Unicode consortium.