Cooker is a evaluation environment of the Rice language. It is a .NET application aimed to run Rice language, and it is built for .NET Framework Ver 4.6.
Cooker has the following features.
The Cooker can run the Rice language.
The Cooker use an ie compatible browser as a console.
You can call the handler that has been written in Rice language to the event of the browser.
Please download the Cooker from the link below.
Please download the source of the Cooker from the link below.
The above Cooker and source file are self-extracting archives of 7z format.
For more information about the Rice language, please refer to the link below.
Installation and uninstallation.
The Cooker is distributed as a 7z format self-extracting archive. Please execute the downloaded .exe file and the necessary files will be expanded.
Cooker.exe is the body of the Cooker.
Cooker does not use the registry. In other words, special uninstallation is not necessary. Please delete the files created by the installation and uninstallation will be completed.
How to use Cooker.
Cooker is a really simple application. If you follow the points described below, you can immediately run the Rice program.
The Rice source file that is the entry point of execution with Cooker must have the extension ".cook". Cooker determines whether it is a Rice source file for Cooker by extension.
Rice source file which does not become the entry point of execution has no restriction on the extension.
Please refer to the following link for the requirements that Rice source files should have.
The Rice source code prepared by the chain of file calls starting with the .cook file must have the definition of the main class and the main class must have the definition of the "start ()" method.
The "open method void start ()" method of the main class becomes the entry point of Cooker's Rice code execution.
Please refer to the following link for the entry point of Cooker's Rice code execution.
How to run the Rice program
There are three way that run the Rice program on the Cooker.
The first way is to drop a .cook file to Cooker's icon.
The second way is to run the Cooker and select the .cook file from the file selection dialog.
The first way
It drop the .cook file to Cooker's icon.
It can also be executed by calling the Cooker with the path of the .cook file as an argument from the command prompt.
The second way
It run the Cooker and select the .cook file from the file selection dialog.
The file selection dialog will open by pressing the Ctrl and R keys at the same time.
file selection dialog
Notes for implementation.
Cooker has used the WebBrowser Control compatible with internet explorer as a user interface.
For this reason, there are some limitations when it implement the user interface.
Navigation of browser is impossible.
Cooker uses browser only for user interface. Therefore, some of the functions of the browser are restricted.
The most important thing in the restricted functions is that this browser cannot navigate. Therefore, nothing happens if you click a link.
Since the browser cannot navigate, it is not possible to replace the whole Html of the user interface by a navigation.
Elements of the user interface should rewrite by using a DOM (Document Object Model).
Cooker's browser draws Html in the same rendering mode as Internet Explorer installed in your Windows.
In other words, if your Internet Explorer is ver 10, Cooker's browser will also be in ver 10 mode, if it is ver 12, Cooker's browser will also be in ver 12 mode.
Cooker's browser interprets the Html of the user interface as Html 5 standard. Other Html standards are not supported.
Since Cooker uses Internet Explorer compatible browser, security settings of Cooker's browser is affected by Internet Explorer settings.
Please refer to the link below for details on how to use the Cooker.
It describes installation and uninstallation of the Cooker.
It describes the browser used for the Cooker's user interface and the important points when implementing the user interface.
It describes how to dynamically add classes at startup of the Cooker.
It describes the requirements that source files executed by the Cooker should have.
It describes how to execute the program on the Cooker.
It describes the start point of Cooker program execution.
It describes the end point of Cooker program execution.
It describes Cooker's message and multilingual correspondence.
It describes the initialization of the Cooker at startup.