Web Interface - Revision history

Gmeader: /* Notes */

2022-06-23T18:13:42Z

Notes

Gmeader: /* Notes */

2022-06-23T18:10:00Z

Notes

Gmeader at 19:43, 20 January 2022

2022-01-20T19:43:32Z

Gmeader: /* JS Scripts: Javascript demos */

2022-01-20T19:42:01Z

JS Scripts: Javascript demos

Gmeader: /* JS Scripts: Javascript demos */

2022-01-20T19:41:30Z

JS Scripts: Javascript demos

Gmeader: /* JS Scripts: Javascript demos */

2022-01-20T19:40:44Z

JS Scripts: Javascript demos

Gmeader: /* UI - web apps */

2022-01-20T19:40:15Z

UI - web apps

Gmeader: /* UI - web apps */

2022-01-20T19:39:12Z

UI - web apps

Gmeader: /* UI - web apps */

2022-01-20T19:37:32Z

UI - web apps

Gmeader at 19:36, 20 January 2022

2022-01-20T19:36:15Z

@@ Line 65: / Line 65: @@
 and a JS fiddle like thing for the content of the nodes
-the js methods and such
+the JavaScript methods and such
 https://ace.c9.io/
-the "JS code" will just be an additional property on any object
+The "JS code" will just be an additional property on any object called "Code".
-any JS inside that has access to the properties on the object
+Any JS inside that has access to the properties on the object.
-any JS methods listed in another property called CodeExposedInputs are available as ports on the object
+Any JS methods listed in another property called CodeExposedInputs are available as ports on the object.
-CodeExposedOutputs - this is outputs.  JS can call these outputs and they can be wired from
+CodeExposedOutputs - this is outputs.  JS can call these outputs and they can be wired from.
-otherwise it works the same as what is there now
+Otherwise it works the same as what is there now
-there is a java file for the "servlets" a "web node" in the monkey java code that defines all the URLs that can be accessed.  Each servlet's handler (a java file) is the definition of the arguments for each message (and the response expected) But alas I do not think there is any sort of javadoc maintained thing or other doc other than the code itself.  (a way of formatting a doc from the comments in the code is IMHO the best way to do this)
+There is a Java file for the "servlets" a "web node" in the Monkey Java code that defines all the URLs that can be accessed.  Each servlet's handler (a Java file) is the definition of the arguments for each message (and the response expected). But alas I do not think there is any sort of javadoc maintained thing or other doc other than the code itself.
-The class CLClientWebNode (in java Monkey) is where all the servlets are "registered" for the URLs than you have to look at each servlet for what it expects to get and what it sends back.
+The class CLClientWebNode (in Java Monkey) is where all the servlets are "registered" for the URLs. Then you have to look at each servlet for what it expects to get and what it sends back.
-some also is where the api can send a message to an object and each object class defines what those messages are and there might be hundreds of the out there I do not really know.  In that case the object itself like "User" or "Entity" defines the messages it can respond to.
+Also there is the API that can send a message to an object and each object class defines what those messages are and there might be hundreds of them out there.  In that case the object itself like "User" or "Entity" defines the messages it can respond to.
 ==code==

← Older revision		Revision as of 18:10, 23 June 2022
Line 79:		Line 79:

	otherwise it works the same as what is there now		otherwise it works the same as what is there now
		+
		+	there is a java file for the "servlets" a "web node" in the monkey java code that defines all the URLs that can be accessed. Each servlet's handler (a java file) is the definition of the arguments for each message (and the response expected) But alas I do not think there is any sort of javadoc maintained thing or other doc other than the code itself. (a way of formatting a doc from the comments in the code is IMHO the best way to do this)
		+
		+	The class CLClientWebNode (in java Monkey) is where all the servlets are "registered" for the URLs than you have to look at each servlet for what it expects to get and what it sends back.
		+
		+	some also is where the api can send a message to an object and each object class defines what those messages are and there might be hundreds of the out there I do not really know. In that case the object itself like "User" or "Entity" defines the messages it can respond to.

	==code==		==code==

@@ Line 1: / Line 1: @@
-There is a web interface API, and some web apps you can access in a browser that can talk to the GorillaXR client engine running on a local or remote machine via HTTP.
+There is a web interface API, and some web apps you can access in a browser that can talk to the Monkey client engine running on a local or remote machine via HTTP.
-do: http://localhost:8080 to access the web server running in your local GorillaXR client.
+Open a web browser on: http://localhost:8080 to access the Monkey web server running in your local Monkey client.
 == Required Settings==
@@ Line 43: / Line 43: @@
 ==Authentication==
-if you are running the standalone (not via Steam) you must login. However, the  ClientConfig.json file has a setting '''attemptLoginWithSteam''' that defaults to true and that prevents proper login from happening. '''attemptLoginWithSteam''' must be set to false. Then starting sandalone monkey will prompt you for a username and password.
+if you are running the standalone (not via Steam) you must login. However, the  ClientConfig.json file has a setting '''attemptLoginWithSteam''' that defaults to true and that prevents proper login from happening. '''attemptLoginWithSteam''' must be set to false. Then starting standalone Monkey will prompt you for a username and password.
 Then when you use the web interface and it asks you to login, give the same username and password.

@@ Line 58: / Line 58: @@
 * PropertyManipulationExample - demo of changing proprties
 * ViewZone - displays a report of all the objects in the current zone
-* CubeExample - creates a cube - An example of manipulating object properties and executing inputs inside a CL node, from JS
+* CubeExample - creates a cube which you can then alter the properties of - An example of manipulating object properties and executing inputs inside a CL node, from JS
 * Spheres - creates many spheres in the current zone

@@ Line 58: / Line 58: @@
 * PropertyManipulationExample - demo of changing proprties
 * ViewZone - displays a report of all the objects in the current zone
-* CubeExample - creates a cube
+* CubeExample - creates a cube - An example of manipulating object properties and executing inputs inside a CL node, from JS
 * Spheres - creates many spheres in the current zone

@@ Line 48: / Line 48: @@
 ==UI - web apps==
-* Console is a way to type interactive commands to Monkey (currently not maintained, so it will not be very useful)
+* CONSOLE is a way to type interactive commands to Monkey (currently not maintained, so it will not be very useful)
-* Status - displays the status of the Monkey system
+* STATUS - displays the status of the Monkey system
-* Zone list - displays a list of active zones
+* ZONE LIST - displays a list of active zones
-* JS modules - tool for managing JS modules
+* JS MODULES - tool for managing JS modules
-* JS scripts - example Javascript demos
+* JS SCRIPTS - example Javascript demos
 === JS Scripts: Javascript demos===