J Application Library
The J application library is a collection of scripts, tutorials and other files that may be added to the distribution.
- For the user, there is a Package Manager for installing addons and updating the core library directly, assuming there is an Internet connection. Once installed, addons become part of the normal J system.
- For the developer, there is a formal method of defining addons, and the use of Subversion for source code management and an automated build system.
The addons and the base library can be installed/upgraded from within the J session, from the distribution repository over the Internet, see Package Manager.
The three main sources for the library are:
- base library - the distributions contain a base library that is required to support the development system.The source for this library is the Subversion repository at , see Subversion/Base.
- addons collection - these are additional modules that can be installed as extensions to the distribution. The source for these is the subversion repository at http://www.jsoftware.com/svn/addons, see Addons/Versioning.
- other contributed scripts - these are single files formerly from the Scripts page; now they will be located in addons/category/misc. There is no separate addons for each script, instead they are distributed together inside a collective category/misc addon, see misc.
Addons are installed in a two-level directory under the local addons directory, for example:
jpath '~addons/web/gethttp' /home/elmo/j8/addons/web/gethttp
Directory ~addons/config is reserved for configuration files, and is not an addon.
All directory names are in lower case.
The load and require verbs support shortnames matching the directory names, for example
load 'web/gethttp' load 'convert/misc/base64'
are equivalent to:
load '~addons/web/gethttp/gethttp.ijs' load '~addons/convert/misc/base64.ijs'
See also the Addons Developers Guide.