File Format: scripts.dcf


[scripts]

This section contains only 1 key, "count". This key contains the number of script sections.

[scriptN]

There are N of these sections, called script0 to scriptN. Each section desribes a particular script. Depending upon the information available, DCFactory will behave differently. Lets look at an example:
[script1]
type=tool
name=cygwin1
script=http://krypt.dyndns.org:81/dcfactory/scripts/cygwin1.bas
scriptname=cygwin1.bas
url0=http://www.dcvision.com/dcfactory/tools/cygwin1.zip
url1=http://www.jonnyroberts.co.uk/dcfactory/cygwin1.zip
url2=http://www.dolooprecords.com/doloop/artist/krypt/mini/cygwin1.zip
remotename=cygwin1.zip
localname=cygwin1.dll
install=cygwin_install
uninstall=cygwin_uninstall
version=1.1
description=Support library for many tools.
size=645632
crc=0
This is a script of type "tool", meaning it's used by other scripts, but has no tasks of it's own. It's named cygwin1, and the script parameter points to the URL where scriptname can be downloaded. If this script requires support files (called remotename, which must be ommited if no urlN keys are present), their urls must be listed in the urlN keys. N can be from 0 to 9 in this case. If localname is set, then the brose local filename option becomes enabled in the download suppor files dialog, if it's absent, this option will be disabled. version contains the version available at the script URL. description is pretty self-explanitory. size should be set to the size of localname if it exists. crc should for now always be 0.

This file must be hosted on a web server, and how to set a simple one up for testing purposes will be detailed later in this guide. However, if you don't want to set one up, you may simply place your script into the scripts\ directory of DCFactory, and modify the [onload] section of dcfactory.ini to run your _load sub.

<< dcfactory.ini | news.dcf >>