What Open/ed looks like in full flight.

[Greg Field]

For those who may be interested, this is what Open/ed looks like in full flight.

See the attached screen shot.

This is running on the Mac using the third party terminal application iTerm2.

There are two windows running, each with multiple tabs.

Each tab has a different source file. Rev 15 Open/ed locks the file you

are working on so you don't accidentally make changes in two places.

The dim text is "locked" lines. Locked lines can not be changed.

The bold text is "tagged" lines. Tagging lines can be used for many very

useful purposes. Here Open/ed is tagging any lines that I have all ready

modified / changed.

On the right of the first window is the help system. You can click on any command

to get its help page.  You may notice some entries are "append","bottom", change",

"delete", "dunload", and "file". These are our old friends fully emulated.

The right hand window shows some text in reverse video. This is a "block" of lines

selected with "from" and "to" commands. A block of lines can be "unloaded", "dunloaded",

duplicated, moved or copied.

On the far right is a function key pop-up. This show what commands the F-keys have

been set to execute. You can see our old friends "xeq", "save", and "file" which can be

actioned with the click of a button, with an F-key or with the mouse.

By pressing one F-key you can compile your code and all the errors found by the

compiler are "tagged" for your attention. A pop-up shows the compiler error message.

Open/ed is used as a sophisticated integrated development environment. 

Open/ed is developed in Open/ed.

I hope you enjoy it. :~)

-Greg.

25th October 2015.