Re: FILEMENU.PM [longish]

[cld@xxxxxxxx (Carl Distefano)]

Reply to note from Peregrine@xxxxxxxx Sat, 20 Jan 2001 21:15:50 EST

-> This suggests some very interesting possibilities for me, and
-> makes me wonder about the management of future applications
-> when -- as must, should or could happen -- XyWrite is
-> reincarnated for use in all places where real writers write
-> and real editors edit.

Must, should, could -- but won't. Let's face it, Jeff, XyWrite is
kaput. Finished; done for. Dead, lifeless; deceased, demised,
departed, defunct, extinct; late, gone, no more; inanimate; out of
the world, taken off, released; dead and gone; dead as a doornail,
dead as a doorpost, dead as a mutton, dead as a herring, dead as
nits; launched into eternity, gone to one's eternal reward, gone to
meet one's maker, pushing up daisies, gathered to one's fathers,
numbered with the dead. And it ain't coming back, any more than the
Romanovs are coming back to Russia. We are the Xyaspora, the
keepers of the flame, and when we go, that's it. Anyone on this
list have kids who use XyWrite? I didn't think so.

-> Assigning different parameters to different workgroups or
-> workstations within a newsroom, for instance, so reporters
-> would boot to specific working directories and have customized
-> quick access to various file resources for research, etc. ...

Hmmm, I think that's the kind of thing that NOSes -- network
operating systems -- are designed to do. What I'm after with my
MACHINE.ID ploy is simple portability. I want to be able to
maintain one set of customization files -- .INT, .DFL, .KBD, .U2 --
for all of my machines; the alternative is headache-inducing. For
this purpose, MACHINE.ID works quite well.

--
Carl Distefano
cld@xxxxxxxx
http://users.datarealm.com/xywwweb/