| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| custom:javascript [2019/05/06 02:05] – [Output] Document the PETSCII '\r' vs. Ctrl-A[ thing digital man | custom:javascript [2023/08/04 19:24] (current) – [Input] A little more clarity on console.getbyte() digital man |
|---|
| |
| You can learn about the core JavaScript language and object model from the following documents: | You can learn about the core JavaScript language and object model from the following documents: |
| * [[http://developer.mozilla.org/en/JavaScript/Guide|Core JavaScript Guide]] ([[http://developer.mozilla.org/docs/Core_JavaScript_1.5_Guide|Historic: 1.5]]) | * [[https://developer.mozilla.org/en-US/docs/Web/JavaScript|Core JavaScript Guide]] ([[http://developer.mozilla.org/docs/Core_JavaScript_1.5_Guide|Historic: 1.5]]) |
| * [[http://developer.mozilla.org/en/JavaScript/Reference|Core JavaScript Reference]] ([[http://developer.mozilla.org/docs/Core_JavaScript_1.5_Reference|Historic: 1.5]]) | * [[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference|Core JavaScript Reference]] ([[http://developer.mozilla.org/docs/Core_JavaScript_1.5_Reference|Historic: 1.5]]) |
| |
| JavaScript is an established, mature scripting language syntactically similar to C++ and Java. | JavaScript is an established, mature scripting language syntactically similar to C++ and Java. |
| [[https://developer.mozilla.org/en/Core_JavaScript_1.5_Guide/JavaScript_Overview#JavaScript_and_Java|JavaScript is not Java]]. | [[https://developer.mozilla.org/en/Core_JavaScript_1.5_Guide/JavaScript_Overview#JavaScript_and_Java|JavaScript is not Java]]. |
| |
| The ECMA and ISO standards organizations have standardized the core JavaScript language in [[http://developer.netscape.com/docs/javascript/e262-pdf.pdf|ECMA-262]] (ECMAScript) and ISO-16262. | The ECMA and ISO standards organizations have standardized the core JavaScript language in [[https://262.ecma-international.org/5.1/ECMA-262.pdf|ECMA-262]] (ECMAScript) and ISO-16262. |
| |
| ===== Baja and JavaScript ===== | ===== Baja and JavaScript ===== |
| Modified stock ''.js'' files should be placed in your Synchronet ''[[dir:mods]]'' directory to prevent over-writing by future upgrades. | Modified stock ''.js'' files should be placed in your Synchronet ''[[dir:mods]]'' directory to prevent over-writing by future upgrades. |
| |
| ===== Integration ===== | ===== Invocation ===== |
| |
| JavaScript files can be executed from: | JavaScript files can be executed / invoked from: |
| * [[:server:terminal|Terminal Server]] | * [[:server:terminal|Terminal Server]] |
| as a timed event, external program (door), login/logon/newuser module, | as a timed event, external program (door), login/logon/newuser module, via the ''EXEC'' sysop command |
| basically anywhere a Baja module or executable can be launched | ((basically anywhere a Baja module or native or MS-DOS executable can be launched)) |
| * [[:server:web|Web Server]] | * [[:server:web|Web Server]] |
| dynamically generates HTML files, | dynamically generates HTTP responses (e.g. HTML/CSS content), |
| see ''[[dir:web]]/root/*.ssjs'' | see ''[[dir:web]]/root/*.ssjs'' |
| * [[:server:ftp|FTP Server]] | * [[:server:ftp|FTP Server]] |
| inbound mail processors may be written in JavaScript, | inbound mail processors may be written in JavaScript, |
| see ''[[dir:exec]]/[[module:mailproc_example]].js'' and ''[[dir:ctrl]]/[[config:mailproc.ini]]'' | see ''[[dir:exec]]/[[module:mailproc_example]].js'' and ''[[dir:ctrl]]/[[config:mailproc.ini]]'' |
| * [[:util:jsexec|JSexec]] | * [[:util:JSexec]] |
| some script files may be executed outside of Synchronet (e.g. as a CGI script or daemon) using jsexec, | some script files may be executed outside of Synchronet (e.g. as a CGI script or daemon) using [[util:JSexec]], |
| examples: ''ircd.js'', ''newslink.js'' | examples: ''ircd.js'', ''newslink.js'' |
| |
| From the Terminal Server, a JavaScript file is executed on a native command-line by placing a question mark (''?'') at the beginning of the command-line before the JavaScript file name (in [[util:scfg]]). It is not necessary to specify the ''.js'' portion of the file name on the command-line. For example, the command-line to execute the file ''[[dir:exec]]/newslink.js'' would be "''?newslink''" or "''?newslink.js''". | From the Terminal Server, a JavaScript file is executed on a native command-line by placing a question mark (''?'') or asterisk (''*'') at the beginning of the command-line before the JavaScript file name (in [[util:SCFG]]). It is not necessary to specify the ''.js'' portion of the file name on the command-line. For example, the command-line to execute the file ''[[dir:exec]]/newslink.js'' would be "''?newslink''" or "''*newslink''". |
| |
| From within a Baja module, a JavaScript file may be executed using the following Baja code: | From within a Baja module, a JavaScript file may be executed using the following Baja code: |
| <code baja> | <code baja> |
| exec "?modname" # where modname is the JavaScript file. | exec "?modname" # where modname is the JavaScript filename or base filename. |
| | </code> |
| | or: |
| | <code baja> |
| | exec "*modname" # where modname is the JavaScript filename or base filename. |
| | </code> |
| | or: |
| | <code baja> |
| | exec_bin "modname" # where modname is the JavaScript filename or base filename. |
| </code> | </code> |
| |
| ===== Object Model ===== | ===== Object Model ===== |
| |
| | ''log()'' | Yes | Yes | N/A | N/A | | Yes((following the log-level argument)) | Displayed/logged on the server only | | | ''log()'' | Yes | Yes | N/A | N/A | | Yes((following the log-level argument)) | Displayed/logged on the server only | |
| | ''console.print()'' | Yes | No | No | Yes | Telnet-IAC, Ctrl-A | Yes | | | | ''console.print()'' | Yes | No | No | Yes | Telnet-IAC, Ctrl-A | Yes | | |
| | ''console.write()'' | Yes | No | No | PETSCII only | Telnet-IAC | Yes | No line-counting/auto-pause | | | ''console.write()'' | Yes | No | No | Yes | Telnet-IAC | Yes | No line-counting/auto-pause | |
| | ''console.writeln()'' | Yes | No | Yes | PETSCII only | Telnet-IAC | Yes | No line-counting/auto-pause | | | ''console.writeln()'' | Yes | No | Yes | Yes | Telnet-IAC | Yes | No line-counting/auto-pause | |
| | ''console.putmsg()'' | Yes | No | No | Yes | Telnet-IAC, Ctrl-A, [[custom:atcodes|@-Codes]], [[custom:colors|Extra Attributes]] | No | Typically used for displaying text/menu files | | | ''console.putmsg()'' | Yes | No | No | Yes | Telnet-IAC, Ctrl-A, [[custom:atcodes|@-Codes]], [[custom:colors|Extra Attributes]] | No | Typically used for displaying text/menu files | |
| | ''console.center()'' | Yes | No | Yes | Yes | Telnet-IAC, Ctrl-A | No | Text centered on screen | | | ''console.center()'' | Yes | No | Yes | Yes | Telnet-IAC, Ctrl-A | No | Text centered on screen | |
| === Carriage Returns === | === Carriage Returns === |
| If you wish to send a traditional "carriage return" character to the client terminal (i.e. move the cursor to the far left column without advancing to the next line) it is recommended that you use an output method/function that supports [[custom:Ctrl-A codes]] and you send the Ctrl-A ''['' sequences //instead of// an ASCII 13 (''\r'') character. This is required for PETSCII terminal compatibility, where an ASCII 13 character performs a complete "newline" sequence (the equivalent of ''\r\n'') on the client terminal. | If you wish to send a traditional "carriage return" character to the client terminal (i.e. move the cursor to the far left column without advancing to the next line) it is recommended that you use an output method/function that supports [[custom:Ctrl-A codes]] and you send the Ctrl-A ''['' sequences //instead of// an ASCII 13 (''\r'') character. This is required for PETSCII terminal compatibility, where an ASCII 13 character performs a complete "newline" sequence (the equivalent of ''\r\n'') on the client terminal. |
| | |
| | ==== Input ==== |
| | |
| | ^ Method ^ BBS((Terminal Server)) ^ JSexec ^ Notes ^ |
| | | ''read()'' | Yes | Yes | Read up to maxlen (default 128) characters of input | |
| | | ''readln()'' | Yes | Yes | Read a string (line of input) from user, up to maxlen chars (default: 128) | |
| | | ''console.inkey()'' | Yes | No | Wait for a key-press or an elapsed timeout duration | |
| | | ''console.getstr()'' | Yes | No | Get a string of characters from user | |
| | | ''console.getkey()'' | Yes | No | Get a single key-press | |
| | | ''console.getbyte()'' | Yes | No | Get an unprocessed input byte from remote terminal as a number | |
| | | ''console.getnum()'' | Yes | No | Get a number (between 1 and maxnum) from user | |
| | | ''console.getkeys()'' | Yes | No | Get a key from a list of valid keys, or a number | |
| | | ''console.gettemplate()'' | Yes | No | Get a string conforming to a provided input template | |
| | |
| | ==== Prompt ==== |
| | |
| | Often you'll want your script to prompt the user for some input (e.g. a string of text or a single key). A prompt involves both //output// (first, from the BBS) and //input// (from the user): |
| | |
| | ^ Method ^ BBS((Terminal Server)) ^ JSexec ^ Notes ^ |
| | | ''prompt()'' | Yes | Yes | | |
| | | ''confirm()'' | Yes | Yes | | |
| | | ''deny()'' | Yes | Yes | | |
| | | ''console.yesno()'' | Yes | No | | |
| | | ''console.noyes()'' | Yes | No | | |
| | | ''console.mnemonics()'' | Yes | No | | |
| | |
| ===== See Also ===== | ===== See Also ===== |
| * [[http://synchro.net/docs/jsobjs.html|Synchronet JavaScript Object Model]] | * [[http://synchro.net/docs/jsobjs.html|Synchronet JavaScript Object Model]] |
| * [[:custom:index|Customization]] | * [[:custom:index|Customization]] |
| |
| {{tag>javascript}} | {{tag>javascript petscii}} |
| |
