If you've just done the 'installation' part of this tutorial you should now be looking at a blank script. If not, find one (it's probably called "new script.txt" and drag it onto the file icon in the top left of your editor window. The script has three sections to it, separated by blank lines.
The 'define' lines and comment lines each stand alone. You can move each line around individually and change their order. The procedure, on the other hand, is a block: it starts with a line containing the procedure name, then comes the contents of the procedure, and it ends with a line containing 'end proc'. If you change the order of the parts of the procedure PsyScript will no longer understand what it is. Blank lines can appear anywhere among any of the above things. They just make the script easier for humans to read. PsyScript ignores them.
You should see a message in green below the script that says "No errors found.". This means you can try to run the script right now. It's almost ready to run but not quite, so hit the 'Run' button (little picture of a running person) to see what PsyScript objects to.
You should have seen PsyScript object to your 'define homeFolder' line. It won't run your script until it knows what the script's home folder is. It got the unsatisfactory definition from a line near the top of your script that starts 'define homeFolder'. In a new script, this definition starts off as 'unknown'. You need to set this correctly for the location and name of your project folder.
If it's not obvious to you what to put on that line, in the folder you've just downloaded you will find a file called 'whatsMyPath.html'. Double-click it to open it in your favourite browser. It will show you the path to its folder and supply a line you can copy and paste directly into your script. Here's what it looks like:
Time for a second attempt to run the script. Hit the 'Run' button a second time. You should see another window open and show a dialog like the following:
Normally this dialog would also be showing you a log of the session which just took place but since you didn't do a real experiment, your script had no log commands, so nothing got logged. Nevertheless the fact that you see this dialog shows that you have successfully run your first PsyScript script, so congratulations ! You've done the hard stuff. Now it's just a small matter of getting your script right.
Since you have no results to log it doesn't matter what you set the three fields to. We'll tackle what they mean later. So to get rid of the dialog just hit the 'Finished' button.
Unfortunately it is not possible for the current generation of web browsers to save changes to your script file by updating the script file on your disk. You will have to do it yourself. PsyScript remembers what script file you're working on and what's in it, but you will want to save a copy of the script for use when you're writing up or for use on another computer, so you will want to keep the script in a text file using a text editor like NOTEPAD.EXE (Windows) or TextEdit (Mac).
If you like to work that way, it's safe to keep the text file open the whole time you're working on your script in the PsyScript editor, just occasionally copying your changes back into the file and hitting 'Save'.
The process for starting with an example script is the same as starting with a blank script. The differences will be that the example script will have PsyScript commands in instead of a comment that says "commands go here", and that some of the 'define' lines at the top will have definitions in rather than default values. Those definitions may be incorrect for your use of the script so you should probably check and change them.