Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site psuvax1.UUCP
Path: utzoo!watmath!clyde!cbosgd!ukma!psuvm.bitnet!psuvax1!dae
From: dae@psuvax1.UUCP (Daemon)
Newsgroups: net.text
Subject: Re: WYSIWYG
Message-ID: <1941@psuvax1.UUCP>
Date: Mon, 23-Dec-85 19:25:36 EST
Article-I.D.: psuvax1.1941
Posted: Mon Dec 23 19:25:36 1985
Date-Received: Wed, 25-Dec-85 03:18:54 EST
References: <2252@glacier.ARPA> <927@mcvax.UUCP> <30@cad.UUCP> <11272@ucbvax.BERKELEY.EDU>
Reply-To: dae@psuvax1.UUCP (Dave Eckhardt)
Distribution: net
Organization: Pennsylvania State Univ.
Lines: 20
Summary: Request for interface info

I happened to be musing about varying preferences people have for text
editors.  This led me to wonder about wysiwyg systems--would people
writing them build on top of them emacs-like, vi-like or edt-like (this
list is obviously incomplete), interfaces?  Or is there some set of
similarities among wysiwyg systems for inherent reasons?

I'm very much in ignorance here, not having worked extensively with
anything remotely resembling a wysiwyg text formatter.

So:  wouldn't some of you like to post quick summaries of how these
beasts work, and/or address the question of commonalities among
interfaces?

--Daemon
--
                You can't spell "earthmoving" without vi!
                Or deviant!
                Or alluvium!
                Or...
                Or...