Scripting Oolite with JavaScript - Revision history

Cholmondely: /* See Also */ Added another link

2025-02-13T06:35:59Z

‎See Also: Added another link

Cholmondely: /* See Also */ Updated link

2024-06-30T09:11:30Z

‎See Also: Updated link

Phkb: Updating BB links

2024-02-29T02:44:29Z

Updating BB links

Hiran: /* See Also */

2023-12-20T23:18:30Z

‎See Also

Hiran: /* Using JavaScript */

2023-12-20T23:17:40Z

‎Using JavaScript

Hiran: /* script.js File Template */

2023-08-28T07:33:17Z

‎script.js File Template

Hiran: /* script.js File Template */

2023-06-21T14:45:25Z

‎script.js File Template

Hiran: /* script.js File Template */

2023-06-21T12:27:16Z

‎script.js File Template

Cholmondely: /* See Also */ Added another link

2023-06-07T17:07:03Z

‎See Also: Added another link

Cholmondely: /* See Also */ Added another link

2023-03-04T19:18:35Z

‎See Also: Added another link

@@ Line 533: / Line 533: @@
 * [[Oolite Javascript basics]] - 2022 essay by [[User:Massively Locked|Massively Locked]]
 * [https://developer.mozilla.org/en/JavaScript/Reference Mozilla JavaScript reference pages] (check for JavaScript 6)
 * [[Oolite JavaScript event handler reference]]
 * [[Oolite JavaScript object model]]

@@ Line 539: / Line 539: @@
 * [[Javascript Operators]]
 * [[Handling OXP Dependencies with JavaScript]]
-* [[Optimization tips]]
+* [[Javascript optimization tips]]
 * [https://bb.oolite.space/viewtopic.php?p=221738#p221738 Writing a debug message into the latest.log] (2014)

@@ Line 1: / Line 1: @@
-[[Oolite]] 1.68 and later supports scripts written in [http://en.wikipedia.org/wiki/ECMAScript ECMAScript] (more commonly known as [http://en.wikipedia.org/wiki/JavaScript JavaScript]) in addition to its traditional model based on [[property lists]]. This page provides an overview of how JavaScript is used in Oolite. The page [[Oolite JavaScript Reference: object model]] provides reference for Oolite-specific objects and methods. The page [[Oolite JavaScript Reference: World script event handlers]] provides reference for the event handlers Oolite supports. The language standards and some tutorials can be found through the Wiki links provided above. The announcement [http://aegidian.org/bb/viewtopic.php?p=130332#p130332 here] may be of use (scroll down to "Javascipt").
+[[Oolite]] 1.68 and later supports scripts written in [http://en.wikipedia.org/wiki/ECMAScript ECMAScript] (more commonly known as [http://en.wikipedia.org/wiki/JavaScript JavaScript]) in addition to its traditional model based on [[property lists]]. This page provides an overview of how JavaScript is used in Oolite. The page [[Oolite JavaScript Reference: object model]] provides reference for Oolite-specific objects and methods. The page [[Oolite JavaScript Reference: World script event handlers]] provides reference for the event handlers Oolite supports. The language standards and some tutorials can be found through the Wiki links provided above. The announcement [https://bb.oolite.space/viewtopic.php?p=130332#p130332 here] may be of use (scroll down to "Javascipt").
 == Using JavaScript ==
@@ Line 445: / Line 445: @@
 === AppleMacs ===
-... Strict semicolon parsing is a Mac thing. Windows and Linux use GNUstep to parse plists and that apparently is more relaxed syntax-wise than whatever it is that the Mac uses. [[User:Another_commander|Another_commander]] from [http://www.aegidian.org/bb/viewtopic.php?p=262814#p262814 A possible solution?] (2018).
+... Strict semicolon parsing is a Mac thing. Windows and Linux use GNUstep to parse plists and that apparently is more relaxed syntax-wise than whatever it is that the Mac uses. [[User:Another_commander|Another_commander]] from [https://bb.oolite.space/viewtopic.php?p=262814#p262814 A possible solution?] (2018).
 == What your computer will do with the Javascript ==
-  The JavaScript is not interpreted directly, but rather is compiled to bytecode at load time. (The compiled bytecode is stored in Oolite’s cache. The exception is the eval() function, which compiles and then runs its argument, but there should be no reason to use this in Oolite except in the debug console script.) Any overhead related to parsing is thus a one-time cost. However, as it’s a completely dynamically typed language, opportunities for type-based optimizations are very limited. On the other hand, some types such as “small” integers (in the range ±1 billion and a bit) can be special-cased easily at run time. ([http://www.aegidian.org/bb/viewtopic.php?p=47013#p47013 Jens Ayton/Ahruman (2008)]
+  The JavaScript is not interpreted directly, but rather is compiled to bytecode at load time. (The compiled bytecode is stored in Oolite’s cache. The exception is the eval() function, which compiles and then runs its argument, but there should be no reason to use this in Oolite except in the debug console script.) Any overhead related to parsing is thus a one-time cost. However, as it’s a completely dynamically typed language, opportunities for type-based optimizations are very limited. On the other hand, some types such as “small” integers (in the range ±1 billion and a bit) can be special-cased easily at run time. ([https://bb.oolite.space/viewtopic.php?p=47013#p47013 Jens Ayton/Ahruman (2008)]
 == Understanding Javascript ==
@@ Line 528: / Line 528: @@
 In trunk, protoChain(player.ship) returns “PlayerShip: Ship: Entity: Object”. In Oolite v.1.74, you get “Object: Object: Object: Object”, which is distinctly wrong albeit mildly amusing to fans of Catch-22. In either, protoChain(new Vector3D) returns “Vector3D: Object”, and protoChain([]) returns “Array: Object”. It also deals with (''i.e.'', correctly lies about) primitive values; protoChain(5) returns “Number: Object”.
-''Note that Ahruman's masterpiece versions of Oolite came after this article - v.1.76.1 & v.1.77.1: the Article is [http://www.aegidian.org/bb/viewtopic.php?f=4&t=8968 Understanding JavaScript, maybe]''
+''Note that Ahruman's masterpiece versions of Oolite came after this article - v.1.76.1 & v.1.77.1: the Article is [https://bb.oolite.space/viewtopic.php?f=4&t=8968 Understanding JavaScript, maybe]''
 == See Also ==
@@ Line 540: / Line 540: @@
 * [[Handling OXP Dependencies with JavaScript]]
 * [[Optimization tips]]
-* [http://www.aegidian.org/bb/viewtopic.php?p=221738#p221738 Writing a debug message into the latest.log] (2014)
+* [https://bb.oolite.space/viewtopic.php?p=221738#p221738 Writing a debug message into the latest.log] (2014)
 * [http://blog.wolfire.com/2009/07/linear-algebra-for-game-developers-part-1/ Linear algebra for game developers] (First of 4 parts, recommended by Ahruman in 2010)
 === History ===
-* [http://aegidian.org/bb/viewtopic.php?f=6&t=2784 Anyone want to write scripts using JavaScript?] ([[David Taylor|Dajt]], 2007)
+* [https://bb.oolite.space/viewtopic.php?f=6&t=2784 Anyone want to write scripts using JavaScript?] ([[David Taylor|Dajt]], 2007)
 === Updating Javascript/Spidermonkey ===
-* [http://www.aegidian.org/bb/viewtopic.php?p=275357#p275357 Issues with updating] (2021)
+* [https://bb.oolite.space/viewtopic.php?p=275357#p275357 Issues with updating] (2021)
 [[Category:Oolite]]
 [[Category:Oolite scripting]]

@@ Line 532: / Line 532: @@
 == See Also ==
 * [[Oolite Javascript basics]] - 2022 essay by [[User:Massively Locked|Massively Locked]]
-* [https://developer.mozilla.org/en/JavaScript/Reference Mozilla JavaScript reference pages]
+* [https://developer.mozilla.org/en/JavaScript/Reference Mozilla JavaScript reference pages] (check for JavaScript 6)
 * [[Oolite JavaScript event handler reference]]
 * [[Oolite JavaScript object model]]

@@ Line 3: / Line 3: @@
 == Using JavaScript ==
-Currently, JavaScript is supported for “worldScripts”, that is, as a replacement for scripts in ''script.plist'' and shipScripts, that acts as expansion for the ships AI. While a ''script.plist'' file may contain any number of separate scripts, a single JavaScript file may contain only one script.
+Currently, JavaScript 6 is supported for “worldScripts”, that is, as a replacement for scripts in ''script.plist'' and shipScripts, that acts as expansion for the ships AI. While a ''script.plist'' file may contain any number of separate scripts, a single JavaScript file may contain only one script.
 If your OXP only uses one script, place a JavaScript file named ''script.js'' (or ''script.es'') in the OXP’s ''Config'' directory. If you wish to use multiple scripts, you may instead create file named ''world-scripts.plist'' in the ''Config'' directory. This [[property list]] file should consist of an array of worldScript names; the named scripts should exist in a directory named ''Scripts'' inside your OXP. As with most “atomic” files (files which cannot be merged), such script files must have a unique name to avoid conflicts with other OXPs. Using the [[world-scripts.plist]] method, you can combine JavaScript, plist and OOS scripts however you wish.

@@ Line 435: / Line 435: @@
+{
      log(this.name, "viewDirectionChanged(" + viewString + ")");
+}

@@ Line 37: / Line 37: @@
+{
      log(this.name, "gameResumed()");
+}

@@ Line 42: / Line 42: @@
+{
      log(this.name, "playerWillSaveGame()");
+}