The preferred way to open cogscripts with Scribe is to add a link to Scribe in the right-click menu of .cog files. But you can use any method that sends the path of the cog to Scribe on the command line. General instructions for all Windows operating systems are given below.
Go to the Control Panel and open Folder Options. In the dialogue box that appears, select the File Types tab. Find the file type for .cog files. If it's not there, create it. In whatever way is provided, view the Advanced settings for the file type. You should see a box listing the actions that can be performed on cog files (such as open).All right, Scribe should now be configured. Enjoy using it. If you find an error with Scribe or something that needs to be improved, email me. Feedback is appreciated.Create a new action called Scribe and give the path for the Scribe exe in the text box for the Application's path. Directly after Scribe's path, add "%1" - with the quotation marks (Windows may add it automatically when you accept the settings). That's all you have to enter for the action settings. Now, when you right click on a cogscript file, you should see a link to Scribe in the menu.
- SaberMaster.
for([statement1[, statement1]]; [condition]; statement2[, statement2]) // optional code
This will probably be the last release of Scribe. It completely perfoms the task it was written to accomplish, and there are no known errors with it. This does not mean that I will no longer support Scribe. If any bug is found, I will try to release a new version to fix the error.
Some time in the future, I will rewrite my cogscript parser. The original version of the parser, written in QuickBASIC, is awkward for what it has grown into. Later, when I have the opportunity, I will write a new parser in a better language that will combine parsing, logical error reporting, and code output into one efficient program.