1. Screens 2. ??? 3. Profit

[Whammo]

We're beginning to have some understanding of a way to manipulate screens.
Moving around screen codes is extremely fast and cool. Taking user input is really easy and clean.
We can select which screen we want to view. Where do we want to take this?
Moving from screens to lines is the next step. Why select lines?
Getting address's and lengths of file names of your choosing, from your current disk, onto the stack by selecting lines of a directory screen is a Disk Auto Menu. Something that is so ubiquitous requires no further description.
But we're moving around screen code! By opening the current screen as a file, we get back PETSCII, and the filename is the part in the line between quotes.
That's where this is going, it's all done but the coding. I'm open to ideas. One I have is,
A method for users to add key press/word/object file associations.

Some preliminary code demonstrating opening the screen as a file and saving to a specified address.

: ssave ( addr -- )
19 emit                    \ home crsr
3 device 0                 \ screen 0 name length
0 1 255 open ioabort  \ fn sa 
clrchn 1 chkin ioabort
1000 0 do chrin readst if drop unloop
then over i + c! loop
clrchn 1 close 8 device drop
;