[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Re: [zzdev] :zz: "Advanced UI components" - vs. zzReligion? (wuz R e: [zzdev] Re: [zzdev] :gzz: d.system (wuz Re: [zzdev] :gzz: Alte ring " system list" (wuz Re: [zzdev] :gzz: Story of an unsuspected crash spi ral (v.0706)
- To: ted@xxxxxxxxxx
- Subject: Re: [zzdev] :zz: "Advanced UI components" - vs. zzReligion? (wuz R e: [zzdev] Re: [zzdev] :gzz: d.system (wuz Re: [zzdev] :gzz: Alte ring " system list" (wuz Re: [zzdev] :gzz: Story of an unsuspected crash spi ral (v.0706)
- From: Tuukka Hastrup <Tuukka.Hastrup@xxxxxx>
- Date: Wed, 19 Jul 2000 11:24:01 +0300 (EEST)
- Cc: zzdev@xxxxxxxxxx
- In-reply-to: <3.0.6.32.20000716144809.008319f0@xxxxxxxxxxxxxxxxxxx>
On 16 Jul, Ted Nelson wrote:
> Tuukka asks--
>
>>Could it
>>already be time for some advanced UI components?
>
> I'm not sure what you're referring to,
> but I don't want any of the standard PARC stuff around !-)
>
> Let everything be a cell, or in a cell, or built out of cells.
> Commonly accessible, commonly manipulable, commonly
> viewable.
And I thought these "constraints" were implicit these days =) And what
comes to the PARC stuff, I must admit I believe they've made good
inventions - only implementation wasn't done computers of present in
mind.
What I mean with "advanced UI components" is some stuff that would
bring gzz even with "PARC GUIs". The first thing is some way to run
actions (ie something like menus): a small I-raster that is
easily accessible by a key press, showing all the normal commands in a
tree-like structure.
And IMO it would be much more friendlier towards the user if we had gZZ
check the options the user feeds in - was it really so that you hated
my suggestion that the user could edit a new bindings list anywhere and
then commit it to the system list _after_ the new list has gone through
some sanity checks?
Tuukka
----------------------------------------
E-Mail: Tuukka.Hastrup@xxxxxx
WWW: http://www.iki.fi/Tuukka.Hastrup
ICQ: #11321669