🚀 go-pugleaf

     Boisy,

     I like your idea of enhancing MVue, but I am wondering....

     First, env.file is intended as a system resource, _not_
gshell's.....at least thats my read. Any boot disk including
control, env.sys, and the line 'control -e' in startup, resets
all 16 colors as well as mouse res/side and key repeat info-
becomes the new system defaults, even if MVue is never invoked. This
makes control the nicest Level2 system utility I have ever seen.
     Whats missing is the ability to assign slots to gshell, and
this is what we should add to env.file- four lines to assign
fore, back, border, and hilite slot #s (not colors- slots).

     My MVue dream upgrade is a CMDS window. This would simply
be a phantom dir screen with a set of systemwide AIF's and
matching icons loaded at boot.

     There are certain programs (Dyna Star/Spell/Form/Calc etc)
that I use almost anyplace, and while MVue does store AIF info on
the fly (allowing one to play games with AIF.file placement and
therefore iconify data files found in lower directories), the only
way to launch a new data file is to click directly on an AIF. Any
idea how many copies of AIF.doc (dynastar) exist on my hard disk?
I have gone as far as banging a shell and using edit to make a
file consisting of a single space, just so I could name this file
'newtext.doc' and so get a clickable launch pad.
     With a sliding 'launch window' available in any data dir I
could really defrag this sucker by plucking many direct AIF's
out. Besides, if the icons for my most used programs are in RAM
since boot, there will not be a need to listen to the old Seagate
(nuk, nunuk, nunununukk, nuk nik nik, brrrrmpppthhpppppttt nuk)
for as long after clicking a folder.
     Extended execute path is neat idea! Always wanted to have
more than one.
                              -ricku