 | |
 | |
 | ||||||
contents
| 4 - Starkits Imagine having a simple directory and file structure, where all application scripts, standard packages, compiled extensions, documentation, images and other binary data resides. That's not so hard - in fact, it is most likely common practice among many developers already. Imagine also having a well-defined way of storing both such an application and all its support files, and the language interpreter itself. Then deployment would become a matter of picking up all the relevant pieces, shipping it to the target machine somehow, and it would run out of the box. Suppose furthermore that the structure could be wrapped into single self-contained files, in a space efficient compressed form, and that these file could be "executed" without unpacking, and without altering a single line in the application. This, in a nutshell is what Starkits are all about. A Starkit is a packaging mechanism for delivering applications in a self-contained, installation-free and portable way. Starkits are a development of an earlier work called “Scripted Documents” by Coen Siegerink [7]. 4.1 - Starkits overview 4.2 - Starkits - a simple example 4.3 - Using packages in Starkits 4.4 - Multi-platform binary extensions 4.5 - Kitten - a collection of binary extensions 4.6 - Starpacks 4.7 - Constructing a Starpack | see also | ||||
| | | | | | |
| | |