(SEXX) Tag: Reverted |
m (Reverted edits by 94.233.241.205 (talk) to last revision by Kelbaz) Tag: Rollback |
||
| Line 1: | Line 1: | ||
Win96 Run Time, sometimes abbreviated as WRT, is the runtime behind the Windows 96 binaries. | |||
== Features == | |||
A script executed with the WRT will behave differently than a normal script. Firstly, this script will be able to use <code>FS</code>, <code>FSUtil</code>, <code>WApplication</code>, <code>StandardWindow</code>, <code>registerApp</code> and <code>deregisterApp</code> without having to use the <code>w96</code> namespace before. these script will also be able to use the WRT module API where the <code>module</code> object is available for exporting data and <code>include</code> for getting module exported data. Scripts executed with the WRT will also be executed in an asyncronous context, so it is possible to use top-level <code>await</code>. | |||
== Usage == | |||
To execute a script using the WRT, there are 2 options: | |||
* Start the script with the following shebang: <code>//!wrt</code> | |||
* Run the <code>wjs</code> command with the path to the script | |||
== History == | |||
The Windows Runtime was introduced in Windows 96 v2 Service Pack 2.<blockquote>"A set of APIs which allow you to easily make apps and include modules, without worrying about the filesystem and stuff like that." | |||
''Windows 96 devs in the rel2sp2 changelog.''</blockquote> | |||
== Shebang == | |||
The shebang is the first line of a binary. The WRT shebang starts with <code>//!wrt</code>. The shebang denotes that this regular file is a WRT bin, and must be the very first line in any WRT application. | |||
=== The binary specification (BSPEC) === | |||
The binary specification (BSPEC) is a way to describe metadata for a WRT bin. It always follows the shebang on the same line, where the cumulative line size must not exceed 256 characters. | |||
The BSPEC is a simple JSON object prefixed with <code>$BSPEC:</code> and contains the following fields: | |||
* <code>icn</code> - The name of the icon to use. | |||
* <code>cpr</code> - The copyright holder of the application. | |||
* <code>dsc</code> - A basic description of the application. | |||
* <code>frn</code> - The display name of the application. | |||
* <code>aut</code> - The application author. | |||
* <code>ssy</code> - The subsystem to use for this application. Can either be <code>gui</code> or <code>cli</code>. | |||
* <code>ver</code> - The version of the application. | |||
Below is an example of a binary specification declaration for the File Explorer application.<syntaxhighlight lang="javascript"> | |||
//!wrt $BSPEC:{"icn":"apps/explorer","cpr":"Copyright (C) Windows 96 Team 2021.","dsc":"System File Explorer","frn":"Explorer","ver":1} | |||
</syntaxhighlight> | |||
Revision as of 17:39, 16 May 2023
Win96 Run Time, sometimes abbreviated as WRT, is the runtime behind the Windows 96 binaries.
Features
A script executed with the WRT will behave differently than a normal script. Firstly, this script will be able to use FS, FSUtil, WApplication, StandardWindow, registerApp and deregisterApp without having to use the w96 namespace before. these script will also be able to use the WRT module API where the module object is available for exporting data and include for getting module exported data. Scripts executed with the WRT will also be executed in an asyncronous context, so it is possible to use top-level await.
Usage
To execute a script using the WRT, there are 2 options:
- Start the script with the following shebang:
//!wrt - Run the
wjscommand with the path to the script
History
The Windows Runtime was introduced in Windows 96 v2 Service Pack 2.
"A set of APIs which allow you to easily make apps and include modules, without worrying about the filesystem and stuff like that." Windows 96 devs in the rel2sp2 changelog.
Shebang
The shebang is the first line of a binary. The WRT shebang starts with //!wrt. The shebang denotes that this regular file is a WRT bin, and must be the very first line in any WRT application.
The binary specification (BSPEC)
The binary specification (BSPEC) is a way to describe metadata for a WRT bin. It always follows the shebang on the same line, where the cumulative line size must not exceed 256 characters.
The BSPEC is a simple JSON object prefixed with $BSPEC: and contains the following fields:
icn- The name of the icon to use.cpr- The copyright holder of the application.dsc- A basic description of the application.frn- The display name of the application.aut- The application author.ssy- The subsystem to use for this application. Can either beguiorcli.ver- The version of the application.
Below is an example of a binary specification declaration for the File Explorer application.
//!wrt $BSPEC:{"icn":"apps/explorer","cpr":"Copyright (C) Windows 96 Team 2021.","dsc":"System File Explorer","frn":"Explorer","ver":1}
