Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!wuarchive!udel!haven.umd.edu!mimsy!mojo!eng.umd.edu!stripes
From: stripes@eng.umd.edu (Joshua Osborne)
Newsgroups: comp.unix.internals
Subject: Re: X11 bashing
Message-ID: <1991Apr26.213221.20605@eng.umd.edu>
Date: 26 Apr 91 21:32:21 GMT
References: <26550@adm.brl.mil> <1991Apr16.210107.41817@eagle.wesleyan.edu> <1991Apr17.040918.12203@Think.COM> <.VXAREE@xds13.ferranti.com>
Sender: news@eng.umd.edu (C-News)
Reply-To: stripes@eng.umd.edu (Joshua Osborne)
Organization: College of Engineering, Maryversity of Uniland, College Park
Lines: 23

In article <.VXAREE@xds13.ferranti.com>, peter@ficc.ferranti.com (Peter da Silva) writes:
> The problem is that they were factoring the problem apart along the wrong
> lines. They implemented basic drawing primitives and assumed that was good
> enough. What they needed to be implementing was visual objects: buttons,
> text panes, windows, etc. Eventually they realised it and built a toolkit
> that let you work with those objects, but because it was in the application
> it put a lot of strain on the protocol, and required real-time response
> from an app.

No they didn't "eventually realise" the need for the server to understand menus,
text editors, and buttons.  That would have forced a Look & Feel onto
applications, which is what they wanted the server NOT to do.  Now users can
choose between 3D and 2D menus, round and square.  Lots of diffrent editors, and
a handful of menus.  Who knows, mabie somone will make pie menus for X.

(You can do most of the button work in the server, likewise for menus once they
are posetd, but that requires a fair amt of memmory in the server)
-- 
           stripes@eng.umd.edu          "Security for Unix is like
      Josh_Osborne@Real_World,The          Multitasking for MS-DOS"
      "The dyslexic porgramer"                  - Kevin Lockwood
"CNN is the only nuclear capable news network..."
    - lbruck@eng.umd.edu (Lewis Bruck)