SDX is an application designed to interact with Starkits (previously called scripted documents). 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 Starpacks (previously called Custom TclKits) and Scripted Document Structure.
sdx subcommands available for use:
(Note that online help is available as sdx help and sdx help cmd)
(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:
set argv [list wrap myapp -prefix mytclkit] source sdx.kit
[Does anyone have wiki pages or web URLs of actual examples of using sdx.kit ??]