[comp.unix.xenix] Coupla questions

cpcahil@virtech.uucp (Conor P. Cahill) (11/09/89)

In article <23791@cup.portal.com>, compata@cup.portal.com (David H Close) writes:
> IMHO, its better!  I have always failed to see any advantage in windows
> smaller than my programs expect.  In general, the larger the window, the
> better.  But "real" windowing systems expect me to get by with several
> tiny windows.  To me, any portion of the screen which my program can't use,

I don't know what "real" windowing systems you have used, but under my 
windowing system I have three main windows which are non-overlapped and 
are of the following sizes:  96 cols/72 rows, 80/32, and 80/44.  Each of these
are using a 9x15 font which is very readable on my 19" monitor.

I even have room left over for my mailer flag, system load average, clock, and
icons of other windows that I use less frequently.


-- 
+-----------------------------------------------------------------------+
| Conor P. Cahill     uunet!virtech!cpcahil      	703-430-9247	!
| Virtual Technologies Inc.,    P. O. Box 876,   Sterling, VA 22170     |
+-----------------------------------------------------------------------+

ORCUTT@cc.utah.edu (11/10/89)

I used a SUN and an HP workstation, and I think that
multiple windows on the screen are wonderful.  However,
on my 640 x 480 VGA, the multiscreen idea seems to
be the best, as the screen is too small for lots of
windows.  If I had a REAL display, though, I would
use X instead of multiscreens...

edhew@xenitec.on.ca (Ed Hew) (11/14/89)

In article <300002@hpspcoi.HP.COM> darko@hpspcoi.HP.COM (David Arko) writes:
>
>There is also multiscreens for serial terminals.  To use this you
>have to have your term type entry in the file /etc/mscreencap
>and then you invoke the capability with the command 'mscreen -n'
>where 'n' is the number if multiscreens desired.  Then you filp
>back and forth between screens by Shift+F1, Shift+Fx...  Depending
>on your terminals capablities this will either clear the screen
>between switches or use the terminals memory to store each screen.
>This is a very vague discription and I will refer you to 'man mscreen'.
>
>This is sort of a poor man's windowing system.

And for those even poorer who don't have a serial terminal with
screen memory, we have "shl".  Shell layers predates SCO's mscreen
implementation by a couple of rev's (it first appeared in 2.2.1 or
2.2.3, it was a while ago).  mscreen requires a terminal capable of
remembering the contents of the ptty's in order to do it's magic.
shl works quite well without this ability.  While it's not quite as
pretty, I remember being very grateful when it first was implimented.
I'll not try to repeat the man page here, but leave that as an
exercise for those interested.

>--David Arko
>darko@hpspcio.hp.com

  Ed. A. Hew       Authorized Technical Trainer        Xeni/Con Corporation
  work:  edhew@xenicon.uucp	 -or-	 ..!{uunet!}utai!lsuc!xenicon!edhew
->home:	 edhew@xenitec.on.ca	 -or-	   ..!{uunet!}watmath!xenitec!edhew
    # Justice is only relative to what you can afford to prove in court.