Interpreter modified by Benedict Jäggi

Benedict Jäggi — Mon, 18 Sep 2023 12:40:20 -0000

--- v1
+++ v2
@@ -1,11 +1,11 @@
 _This is the text copied from the old documentation. For the actual text, visit the [Installation] section._

-For this particular interpreter here, you can just put all the files in any directory and run the interpreter/index.html. All GIML stuff is in the testsite folder inside the interpreter folder.
+For this particular interpreter here, you can just put all the files in any directory and run the _interpreter/index.html._ All GIML stuff is in the _testsite_ folder inside the _interpreter_ folder.

-The GIML-page will be loaded with a function call in the index.html. Later, the browser itself shall do that. You can change the directory and page there. Keep in mind that this is just a prototype.
+The GIML-page will be loaded with a function call in the _index.html._ Later, the browser itself shall do that. You can change the directory and page there. Keep in mind that this is just a prototype.

 Be aware that the testsite has some "faulty" (but working) entries and some errors. They were made to test if the interpreter can handle it.

 E.g.: There is the same file loaded in two gml files. It should give a warning that there is a double entry, despite the "different" paths from the two issuing files.

-The testsite folder or any other folder with a GIML-page should reside OUTSIDE of the interpreter core directory. But because of CORS, there are to much security measures to make such stuff happen "as is", without setting up complex server stuff and so on. I mean, I just want to edit a file and test it out locally. I don't want to set up a whole server infrastructure just to see how a freaking "Markup Language"-file looks on the browser. Damn CORS. So, I just put the GIML-folders into the interpreter folder. Sorry for that. No, not sorry: Damn and curse CORS for that. It made the internet a whole lot more complicated and I don't want to see it on "my" internet. 
+The _testsite_ folder or any other folder with a GIML-page should reside OUTSIDE of the interpreter core directory. But because of CORS, there are to much security measures to make such stuff happen "as is", without setting up complex server stuff and so on. I mean, I just want to edit a file and test it out locally. I don't want to set up a whole server infrastructure just to see how a freaking "Markup Language"-file looks on the browser. Damn CORS. So, I just put the GIML-folders into the interpreter folder. Sorry for that. No, not sorry: Damn and curse CORS for that. It made the internet a whole lot more complicated and I don't want to see it on "my" internet.

Interpreter modified by Benedict Jäggi

Benedict Jäggi — Mon, 18 Sep 2023 12:40:20 -0000

This is the text copied from the old documentation. For the actual text, visit the [Installation] section.

For this particular interpreter here, you can just put all the files in any directory and run the interpreter/index.html. All GIML stuff is in the testsite folder inside the interpreter folder.

The GIML-page will be loaded with a function call in the index.html. Later, the browser itself shall do that. You can change the directory and page there. Keep in mind that this is just a prototype.

Be aware that the testsite has some "faulty" (but working) entries and some errors. They were made to test if the interpreter can handle it.

E.g.: There is the same file loaded in two gml files. It should give a warning that there is a double entry, despite the "different" paths from the two issuing files.

The testsite folder or any other folder with a GIML-page should reside OUTSIDE of the interpreter core directory. But because of CORS, there are to much security measures to make such stuff happen "as is", without setting up complex server stuff and so on. I mean, I just want to edit a file and test it out locally. I don't want to set up a whole server infrastructure just to see how a freaking "Markup Language"-file looks on the browser. Damn CORS. So, I just put the GIML-folders into the interpreter folder. Sorry for that. No, not sorry: Damn and curse CORS for that. It made the internet a whole lot more complicated and I don't want to see it on "my" internet.

Recent changes to Interpreter

Interpreter modified by Benedict Jäggi

Interpreter modified by Benedict Jäggi