|!OutBack character cache/command archive | GetBack for nbWin/xyWin || <compass> | <toc>|
most recent revise 4 july 2001
Clearing the xyWrite command line to run an xpl
pgm wipes out four pieces of information that if
known would let the pgm work as subtly as a function.
Assembling any three of the four isn't difficult
for experienced xpl programmers, but seizing all
four defeated the most ingenious. They'd already
gratefully moved on from v3 to xyDos 4 when
!xyWise came along.
When you press a key where !xyWise's &C replaces BC in your kbd file, !xyWise--besides clearing the CMline--in service to other xpl in effect creates four crucial va$s xyWrite 3 doesn't record. &C profiles and preserves the at-launch:
Frame $P brings the most recent command &C saw back to the CMline, and $P also can write the current file name (nice for file management) or cursor position to the CMline. !xyWise func XC substitute Frame $X loads Help frames and launches !xyWiz programs; you don't even have to type "run." Documentation suggests interesting ways to mix the auxiliaries.
In hope you can spare three of the 36 xyWrite provides, !xyWise asks you to sacrifice s/gs @B, @C, and @D so you can manage the text buffers easily with everyday XyQuest tools. !xyWise uses resources that call on permanent memory (as s/g@[A-Z/0-9], >99 variables, ldpms, and Help frames do) only when no alternative offers itself, but one usually does: Thus !xyWise's runtime libraries, oft-used procedures that occupy memory only during a pgm's run.
The overlay's structure is fragmented for versatility and to minimize memory overhead. No, not as orderly as Help frame programming--confining all procedures and programs to a Help file--but far more memory-conservative. When xyWrite makes so many resources available, an excessive devotion to tidiness is the only explanation I can think of for the impulse to lean exclusively on one instead of using the one best suited to the task.
If you're an xpl programmer or would like to be, take a
look at the xplWise page for more on !xyWise's
structure and information on !xyWise xpl documentation.
No need to groan
|when you must overwrite a carefully constructed crossfile search or do pkunzip command, or you realize you backspaced the wrong text. A vivid example of the way !xyWise expands xyWrite 3 possibilities, !OutBack maintains caches that let you get back commands and characters you took out accidentally or for use later. No stupid menus!|
!OutBack commands archive @B
Automatically @Buffer the command every time you clear the CMline, deleting the oldest of a fixed number with each addition, or keep a @Buffer of most-used commands, tapping your $Keep key to archive a displayed command manually; tap a !xyWiz !B key to delete the displayed command from the @Buffer. You can tap another key to cycle quickly through @Buffered commands. Rotation keys reveal the number of commands archived and advance or reverse the @Buffer, bringing the next or previous command to the CMline.
!OutBack character cache @D
Restore &Deleted or &Backspaced chars to text--anywhere--one by one, LIFO, from the @Delete cache by tapping your new &Get key. Buffering occurs transparently every time you delete and backspace. If you've ever used a word processor that has a like feature you're familiar with the security of knowing you can undo accidental deletions with a key tap, and the convenience of its use as a tool for making small edits.
Why should xyWin and nbWin users be deprived? The !OutBack character cache now also is a standalone port named GetBack--and look, Ma, no &ldpms or @s/gs (it uses a >99 s/g instead of an @s/g). Actually, I once was told that Signature+ (xyWrite 4 for both platforms and xyWin's successor, SmartWords->nbWin) do something like this, but I've never discovered how and I fear it involves (argh) dialog boxes. Fersure, Sig+ stack commands, hence no public port of the !OutBack command archive, hence the different name. I may withdraw GetBack in favor of OutBack for nbWin/xyWin anyway; other dialog boxophobes might prefer OutBack's command stack scheme to the one built into Sig+, which I've never tried. BetterThanAverageTaggingTool for xyWin/nbWin was delayed for the amount of time it took me to debug GetBack. I can't work without it. If you try GetBack with xyDos4, please let me know how it works with that release.
Compass: The table of contents at the end of each linked page at this site lets you shift laterally to other local pages, get back to the xyWrite and xyW/PostScript index page ("overview"), download the zipped files the docs describe, and explore other resources.
more about ...
!xyWise modular utilities !xyWiz
!xyWiz Web assistant
!xyWWWiz & xy/nbWin port
!xyWWWiz html color chart
(you are here)
xyWrite 3+ overlay
+ !OutBack & xy/nbWin port GetBack
xplWise tech reference and instructions
Make legacy apps eternal:
get the NAQ
PostScript Type 1 font xyWrite driver tables
non-xyW kbd notes
Signature+ xpl notes
(see !xyWWWiz documentation) (<7k)
TTG free kernel upgrades:
> xyWrite 3 (see <overview> notes re autoreplace and login ! )
> xyWrite 4--Windows and dos (read FILE.TXT at the link)
||adpFisher nyc 4 july 2001|