A WiKit document consists of Tcl/Tk scripts and MetaKit data, all combined into one file. In a way, WiKit is a file-system inside a file. To manage the contents of the file (data and scripts), a command-line interface has been defined which lets you query, extract, as well as replace information inside the file. 1. Each WiKit document contains at least a '''script section''', where a core set of scripts is stored. 2. There is a '''pages section''' which contains a set of hyperlinked pages, such as this one you're looking at. 3. There's a small but essential '''admin section''', which holds snippets of information controlling the operation of this WiKit document. 4. And finally, there's room for any number of '''extended sections''', used to store data of any type and structure. Due to the way data is managed, the actual number and layout of sections can - ''and will'' - vary over the lifetime of a WiKit document. The '''Command Line Interface''' is a safety feature and testing tool, which allows you to get at any data stored inside any WiKit document without additional software (other than the appropriate [TclKit] runtime for your platform). And if ever things go haywire, you can view and even modify the scripts stored inside WiKit (changes should be made with extreme caution, evidently). Note that the command line interface gives you access to EVERY bit of information stored inside a WiKit document. ---- '''Usage''': '''wikit.tclkit''' -option ... -option [[--]] remaining arguments Options are of the form: * '''Inspection''' - these let you find out more about the type of information stored: -type -type/entry -group-param * '''Fetch information''' - extract information in more or less detail: -type:[field] -type/entry:[field] -group-param: * '''Store information''' - replace information with new contents: -type=file -type/entry=file -group-param=value The '''type''' name is either '''''script''''', '''''pages''''', '''''admin''''', or a user-defined ''extended section name''. The '''entry''' name specifies a specific entry. In scripts, these are ''script names'', in pages they are ''page titles'', in the control section, they are ''group names'', and in the extension sections, they are whatever the ''key field'' of that section is defined to be. The '''field''' specifier in fetch requests is optional and specifies which field to extract verbatim, instead of generating a list of all fields. If present, the name should not include the brackets shown above. There is a more fine-grained access mechanism for information stored in the admin section, which you can access using the third format shown. In this context, '''group''' is the name of the admin entry, and '''param''' specifies a single parameter value in that entry. This allows you to inspect or adjust configuration without having to go through a graphical user interface. Even parameters which are not normally intended to be changed at all are available through this command line interface.