Chapter 12. TODO's

We are going to present here a list of things which we think will be desirable to address in a short-term future:

• Closing Internet Explorer: When displaying a sketch through Internet Explorer the user has to press the Stop button in order to close the window. This is because while the main loop (which is located in the AbstractRunning module) is running on the client's machine, Internet Explorer events are not captured. The main loop has the Application.DoEvents(); but it doesn't solve the problem. The solution seems to be related with threads. If we put the main loop in a different thread the user can close Internet Explorer without problems, but unfortunatlly this has some other drawbacks. Since the control is located in one thread and the code that paints to that control is located in another thread random errors occur. This is a documented issue. In Windows you can not paint from one thread to another.

• Exporting to one unique DLL or EXE file: When exporting a sketch written in a syntax which is not C# the generated files include various DLL files. This is because when the sketch is written in C# the program creates programmatically one instance of the CSharp compiler and builds all the application in one unique EXE or DLL file. But when the sketch is written in another syntax the Running module has to be compiled with another compiler instance different from CSharp and then an independent DLL is created. The solution for this may be merging all the resulting DLL's in one unique DLL or EXE file. There is a suitable application for this called ILMERGE but it only runs in the v2.0 .NET Runtime and doesn't work with Mono.

• Sketches that need more privileges when running through Internet Explorer:

• Decauple Syntax parsing: Now, if we want to add a new syntax in which users can write their sketches (for example Delphi or C++), we have to modify the source code of the Parsing module to handle the new syntax with a new compiler. If there was a way to decauple all this and make the process of supporting new syntaxes more dynamic it would be great.

• Complete Kernel Primitives:

• Complete Java Emulation:

• No more source code distributed with the binaries:

• Support for addicional libraries:

• Ask user for multiple dll exportation:

• Ask user for namespace when exporting to .NET User Control