'''SDX''' is an application designed to interact with [Starkit]s (previously called [scripted document]s).  The acronym now stands for '''Starkit Developer eXtension'''.

(You can find it at http://mini.net/sdarchive/ )

sdx is frequently named [sdx.kit] on systems where extensions are used to
create mappings between files and their interpreters.

Hopefully users of sdx will chime in here with pointers to documentation,
examples of use, tricks, techniques, and more.
The combination of [tclkit] and starkits is a very powerful one.

See also [Starpack]s (previously called [Custom TclKit]s) and [Scripted Document Structure].

----
sdx subcommands available for use:

''(Note that online help is available as '''sdx help''' and '''sdx help''' ''cmd'')''

   sdx addtoc:   deprecated
   sdx eval:   evaluate Tcl from the command line (try "sdx eval parray tcl_platform")
   sdx fetch:   fetch an http file (try "sdx fetch http://wiki.tcl.tk/4.html ")
   sdx ftpd:   runs an FTP server
   sdx httpd:   run a little HTTP server
   sdx httpdist:   synchronize a dir tree over the web (see [http://www.equi4.com/httpdist/])
   sdx ls:   list files, also on windows
   sdx lsk yourstarkit:   List the contents of a starkit
   sdx md5sum:   calculate MD5 sums (probably broken)
   sdx mkinfo <'''NEW'''>:   display info about mk datafile offset/format and the views it contains
   sdx mkshow:   dump Metakit views
   sdx qwrap:   a shortcut for "sdx wrap", creating a runnable compressed starkit from a single Tcl script (avoids having to do "mkdir myapp.vfs/bin/main.tcl" etc, manually)
   sdx ratarx:   reverse actions of a "tar x" command (delete all files also present inside the tarx, leaving only those that differ)
   sdx rexecd:   remote exec server
   sdx sdx:   the code which implements the help functionality
   sdx sync:   copy one tree to another, but only changes (can also deal with SD's)
   sdx treetime <'''NEW'''>:   adjust modtimes in dir trees to match most recent file inside
   sdx unwrap yourstarkit:   Extract the contents of a starkit into a file system. Creates a directory with the name ''[[file root starkit]].vfs''  The directory must not already exist.
   sdx wrap skname:   Takes the contents of the directory '''skname'''.vfs and and creates a starkit with the name '''skname''' from it.  ''Be sure to use the -writable flag if you want your starkit to be writable!''  By default starkits are read-only.

(crc16, pkgIndex, and tree were erroneously listed in an older version of sdx)
----
[LV] from the [starkit] mailing list, [jcw] says:


 You're going to have to create starpacks on the Mac.

Reason: mac files have a "data fork" and a "resource fork".  The .bin 
files are an exchange format which ties them together (along with a bit 
of "finder info").  Catenating anything a the end probably will simply 
be ignored on unpack - which is what happens once you take it to the 
mac and unpack through StuffIt Expander or some such (Mac browsers tend 
to do that automatically, right after download).

If you do it on the Mac, while the forks are distinct, sdx will 
concatenate after the data fork.  Then you can run it through StuffIt 
to create the transferable .bin version.

Running SDX on the Mac takes some trickery, since SDX is command-line 
driven, and the Mac has only tclkit:

   
   1.  Launch tclkit
   2.  In its console, type:
        set argv [list wrap myapp -prefix mytclkit]
        source sdx.kit
   3.  The sdx starkit will perform its work (and exit, I think)

----
[[Does anyone have wiki pages or web URLs of actual examples of using
sdx.kit ??]]

----
[[
[Category Application] | [Category Wikit] | [Category Tclkit]
]]