- Doorbell -- DCS7 CLI
- 21 Sep 2011 04:49:01 pm
- Last edited by Ashbad on 24 Sep 2011 05:55:58 pm; edited 1 time in total
Well, since Kerm said on IRC he would help me by providing some examples for doing file/folder manipulation, I decided to take a quick 3-4 day break from PrizmCity to make my first DCS related program
What I'm essentially aiming for is an alternative way for uber-haxers who hate GUIs or just the DCS GUI in general to go about using doors effectively. I'm thinking for most efficiency, to have a somewhat-condensed system of scripting, with maybe 20-30 commands, all of which with short calling names and simple/rememberable parameter intakes. Some ideas for what I'll try to implement ASAP:
.(Program Name) // runs program
REN (Old Name) (New Name) // renames
MOV (Path) (New Path) // moves file/directory
CPY (Path) (New Path) // copies file/directory
DEL (Path) // deletes
LCK (Program Name) // locks program
HID (Program Name) // hides program
TYP (Program Name) // gets type(s) of fil(s)e in cur directory with name
CD (New Dir) // changes to new directory
CD // shows current directory
NEW (name) [size] [type] // creates new file of name, type, and size. If no type, creates directory and size is ignored
X/Q/QUIT // quits
INF (name) // gives info of given file, including size, locked, hidden, long desc., etc.
CHK // get a program's checksum and display it
Possible candy features later on once the bare bones is finished:
- Possibility of making a new system to pass parameters to a program on running statement
- .DSL (Doors Scripting Language) files which contain pre-written DSL commands, like the bare bones ones above
- Simple variables
- Useful system commands (TIOS)
- Block/control statements (for .DSL files)
- Internal file manipulation
Any ideas, or the such? I should get something working tomorrow.
What I'm essentially aiming for is an alternative way for uber-haxers who hate GUIs or just the DCS GUI in general to go about using doors effectively. I'm thinking for most efficiency, to have a somewhat-condensed system of scripting, with maybe 20-30 commands, all of which with short calling names and simple/rememberable parameter intakes. Some ideas for what I'll try to implement ASAP:
.(Program Name) // runs program
REN (Old Name) (New Name) // renames
MOV (Path) (New Path) // moves file/directory
CPY (Path) (New Path) // copies file/directory
DEL (Path) // deletes
LCK (Program Name) // locks program
HID (Program Name) // hides program
TYP (Program Name) // gets type(s) of fil(s)e in cur directory with name
CD (New Dir) // changes to new directory
CD // shows current directory
NEW (name) [size] [type] // creates new file of name, type, and size. If no type, creates directory and size is ignored
X/Q/QUIT // quits
INF (name) // gives info of given file, including size, locked, hidden, long desc., etc.
CHK // get a program's checksum and display it
Possible candy features later on once the bare bones is finished:
- Possibility of making a new system to pass parameters to a program on running statement
- .DSL (Doors Scripting Language) files which contain pre-written DSL commands, like the bare bones ones above
- Simple variables
- Useful system commands (TIOS)
- Block/control statements (for .DSL files)
- Internal file manipulation
Any ideas, or the such? I should get something working tomorrow.