Starkit

This is no longer the Starkit home page, that has now been moved to:

    https://www.equi4.com/starkit.html

(this page is kept until all reference information listed here has been transferred)

A Starkit is a packaging mechanism for delivering applications in a self-contained, installation-free, and portable way. The name comes from being based on a STandAlone Runtime.

First time here? See Getting started with Starkits on Windows or Getting started with Starkits on Unix.

Purpose of starkits
Where to find starkits
How to use a starkit
How to assemble a starkit
Single-file starpacks
Compatibility issues
Anatomy of a starkit (includes a number of conceptual pictures)
Version IDs provide a way to track versions of starkits
Starsync - a way to download and incrementally update starkits
Starchive - a concept for managing starkit collections and revisions
Background information on Starkits
Other wrapping mechanisms
How to set up starkits as CGI
Placing packages in a starkit
Custom icons for Win32 starpacks
Links to older information
Glossary of terms

Current status

November 2002 - Tclkit 8.4.1 released
September 2002 - Starkits and Tclkit 8.4.0 final, included on the Tcl/Tk 2002 conference CD
There is a Starkit Mailing List to discuss everything related to Starkits, Starpacks, and Tclkit

Papers, presentations

Beyond Tclkit - Starkits, Starpacks and other *stuff by Steve Landers, 9th Tcl/Tk Conference, Vancouver 2002, see [1].
Tclkit, Starkits (still called SDs), and Critcl were presented at EuroTcl Munich, June 2002, see [2] and [3].
SD's, a precursor to Starkits, were presented at the Tcl/Tk 2000 conference in Austin, see [4].

In case you're wondering

The term scripted document is obsolete - it's now a Starkit
The term custom tclkit is obsolete - it's now a Starpack