The term '''Scripted Document''' is obsolete, as of July 2002 it is called a '''[Starkit]''', the new homepage is http://www.equi4.com/starkit/. ---- ''Older notes, pruned but left here for reference...'' ---- There is an emerging [Scripted Document Structure] standard. Early July 2000, [WHD] wrote: '''But is "Scripted Document" the best name? See [Scripted Documents Are Obscure].'' [CL] chatters on scripted documents [http://starbase.neosoft.com/~claird/comp.software-eng/scripted_documents.html]. Anyone have any good help on how to use scripted documents on MacOS (pre-X I guess... MacOS X should work the same way as other OSes with regards to launching apps, right?) What [LV] has found is that if you start up a MacOS tclkit, then do a [source] of the scripted document, then you come close to getting things to work. The missing step is that currently at least, there is a missing environment variable which you need to set before sourcing the scripted document. That step is to do something like: set $::env(PATH) "." ---- See also [sdx] ---- [Category Wikit] | [Category Tclkit] | [Category Scripted Document]