From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: vecera@writeme.com
Message-ID: <91s9u5$hq7$1@nnrp1.deja.com>
References: <91nt3g$t2f$1@nnrp1.deja.com>, <200012200058.AAA18825@whitecrow.demon.co.uk>
Subject: [9fans] Re: Future of Plan9
Date: Thu, 21 Dec 2000 09:45:16 +0000
Topicbox-Message-UUID: 3af5312c-eac9-11e9-9e20-41e7f4b1d025

In article <200012200058.AAA18825@whitecrow.demon.co.uk>,
  9fans@cse.psu.edu wrote:

> > BTW: Is anybody going to port tcl/tk lib to Plan9? Or anything else
> > which
> > will make easy to create menus and buttons and others in apps?
>
> This is my point: acme doesn't use menus or buttons, and it doesn't
> need tcl or tk to produce applications which use it as the user
> interface. But it does affect the style of interface you can have.
> acme doesn't have graphics, so you can't do a WYSIWYG text processor,
> but you could provide an interface to a TeX system with all sorts of
> nifty tools. So the question is not what you think you need, but what
> do you *really* need?

Acme without graphics can offer simply text menu and nothing else.
How will you solve case when you need choose between more choices
(radio buttons) or when you need ask for a value, string... or create
check box, list box?
Take some bigger app (f.e. Netscape) and thing out how could you make
his menu and control in acme...

I very like things simple and minimized but this should not _limit_ you.

vecera


Sent via Deja.com
http://www.deja.com/