View Image

Visral Operating Environment for Python 1) The results from code executed in the four Visral OE's editing PADs are directed to separate document windows. This means command line prompts are unnecessary and work product is kept separate, not intermixed with instructions. 2) Because the output windows are also document editors, comments and images that might be necessary to clarify or augment the result can easily be added. Finished documents can be printed in-part or in-full and saved as RTF files, which can be further edited with MS Word. 3) Besides being able to cut, copy, and paste into a PAD, any selection of code can be run, edited, and then rerun again without the need to retype the entire expression. 4) The more common Python modules are automatically imported with their alias on startup, saving having to constantly re-enter them. There is also a Python priming file for the same purpose that can be user configured. 5) There is syntax coloring, auto indexing, de-indexing, and auto-complete for both variables and methods. There are insertion menus for variables and file names to assist in recollection, as well as alleviating the need for typing them. 6) PAD editor contents, selected or full, can be printed or saved as Python text, RTF, or HTML files. Contents can be loaded from Python text or extracted from RTF files. 7) A 30,000 character rolling history of all executed code is maintained allowing its examination and recovery if needed. 8) The actual Python engines run in processes separate from the editors, meaning if some experimental code caused it to hang, say in an endless loop, all is not lost. Python can be restarted from within Visral, preventing the loss of work and permitting a modified version of the culprit code to be tried again. 9) There are built-in Python methods that permit real-time access to operating system resources while simultaneously pausing code execution until requests have been completed.