|
We make some rather ambitious claims for the mvToolbox in terms of time and cost saving improvements. The means for the savings is the underlying philosophy of the mvToolbox. Like the Amish, the mvToolbox wastes nothing.
The standard editors, ED and UP, treat the items being edited as flat text, detached from everything else. All the editor can do is read items, display them, let you input or change, and file them. The information on the screen is not used at all.
mvToolbox views a program like a map to a much wider structure,
consisting of all the code (internal and external), and all the data.
The mvToolbox is able to save immense amounts of time because it makes use of the information on the screen. It provides linkage between the code and the collections of information that the code represents.
Every program has several kinds of information that just goes to waste. mvToolbox uses that embedded and inferred information.
- OPEN, READ, WRITE, SELECT... - links to files
- CALL, EXECUTE, PERFORM, INCLUDE - links to other modules
- GOSUB and GOTO - links to paragraphs
- Structured code - links to other places in the structure
We call these features Transparency, or Mobility.
|