9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: a@9srv.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme design
Date: Wed,  2 Jun 2004 09:20:19 -0400	[thread overview]
Message-ID: <4d30561ec4fd4a26b45150a2416c002a@9srv.net> (raw)
In-Reply-To: <ACCF003CBA3D09458207DB0CB86AD17D2012AE@XMAIL.asuch.cas.cz>

maybe, but i still don't get it. :-)

or maybe i do and i'm in denial. i see two "content" frames, a tag
frame, and a command frame. what determines which content frame
the commands operate on? how do i know which "content" frame is
which in the tag list?

this model seems to eliminate the tag bar as distinct from the

"normal" frames (which seems good - they break the "all text is
equal" theme that's present elsewhere) but then introduces several
(at least two, possibly more i can't see) new types of "special"
frames. this adds more modes to the operation of the interface,
which is bad. it also significantly increases the amount of mouse
motion needed to execute Tag items (even assuming some magic AI
for tracking which frame you're talking about).

what is it you think this model gains you?

(i'd like to see either multi-line or scrolling Tags, to avoid loosing
bits when the Tag gets too long, and the ability to create Rows at
the top-level like i can with Cols. these are certainly more
incremental (an thus possibly less exciting) than your suggestion,
but i'm pretty sure i can clearly show the benefits.)


  reply	other threads:[~2004-06-02 13:20 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02 12:57 cej
2004-06-02 13:20 ` a [this message]
2004-06-02 15:18   ` plan9
2004-06-03 13:48   ` rog
2004-06-03 14:17     ` lucio
2004-06-03 14:34       ` rog
2004-06-03 15:38         ` kiwane
2004-06-03 15:45           ` rog
2004-06-04  9:19     ` Bengt Kleberg
2004-06-04 10:29       ` Axel Belinfante
2004-06-03  0:54 ` Kenji Okamoto
2004-06-03  0:56   ` Kenji Okamoto
2004-06-03  8:35 ` WLad
2004-06-03  8:40 ` vdharani
2004-06-03  7:58 cej
2004-06-03  8:54 ` Kenji Okamoto
2004-06-03  8:07 cej
2004-06-03  8:52 ` plan9
2004-06-03 13:53 ` rog
2004-06-03 13:55 ` rog
2004-06-05  6:09   ` YAMANASHI Takeshi
2004-06-05 10:07     ` Charles Forsyth
2004-06-05 13:48       ` YAMANASHI Takeshi
2004-06-05 15:50         ` Rob Pike
2004-06-06  2:23           ` YAMANASHI Takeshi
2004-06-06  3:25             ` Rob Pike
2004-06-06  7:24               ` YAMANASHI Takeshi
2004-06-06  8:54               ` vdharani
2004-06-03  8:37 cej
2004-06-03 11:21 cej
2004-06-03 14:59 ` a
2004-06-04  9:12 cej
2004-06-04 11:22 cej
2004-06-07  8:22 cej
2004-06-07 13:43 ` Russ Cox
2004-06-07 13:47 ` boyd, rounin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4d30561ec4fd4a26b45150a2416c002a@9srv.net \
    --to=a@9srv.net \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).