Re: writing html in xywrite

["Steve Hayes" khanyaiis@xxxxxxxx]

On 27 Dec 00, at 20:52, Carl Distefano wrote:

> Steve Hayes writes:
> ≪ Are XPL programs macros?
> ≪
> ≪ Another problem with the versatility of XyWrite. I
> would say that Save-Gets are what most other programs
> call "macros". XPL programs are, well, programs. ≫
>
> The term "macro" is extremely flexible, in my
> experience. In Xy parlance, macro usually refers to a
> simple XPL program consisting of recorded keystrokes or
> a straight-forward series of functions and/or CMline
> commands. Whereas "program" usually (though not always)
> denotes a more complex set of instructions, including
> logical or string operators, evaluative expressions,
> conditional statements, loops, etc. I don't
> associate "macros" with "Save/Gets", though there is a
> keystroke-saving similarity. When Signature was
> introduced, XyQuest tried to abandon the archaic-
> sounding "Save/Get" for the more descriptive (though
> somewhat misleading) "text macro", but, as far as I
> know, the new terminology never caught on. What we call
> Save/Gets the (generally speaking) less technical-minded
> NotaBenieri designate as "Phrases", a non-descript
> locution to my ear, but suum cuique (as those scholarly
> users might protest).

I began computing with CP/M, and was introduced to "macros" by the Osborne
documentation, where it was described as a lot of text associated with a
single key, which XyWrite called a "Save/Get". The Osborne came with
Wordstar, which still has not been surpassed for mail merge - it could draw
in boilerplate text from disk files (quite important in the days of 2 180k
single-sided floppy drives).

> In the WordPerfect world, the term "macro" covers
> everything from a small batch of recorded keystrokes to
> lengthy, structured scripts (there's another fluid term
> for you). To my knowledge, they never use the
> term "program", though clearly that's what the more
> complicated scripts are.

I think MS Word doers much the same thing, except that they change it in
every new version, from macros to Word Basic to Visual Basic for
Applications. Part of the planned obsolescence, no doubt, and also for ease
of virus transmission.


Keep well,

Steve Hayes
E-mail: shayes@xxxxxxxx
  Web: http://www.geocities.com/Athens/7734/steve.htm