[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lojban-beginners] Re: User interfacing in Lojban..
- To: lojban-beginners@lojban.org
- Subject: [lojban-beginners] Re: User interfacing in Lojban..
- From: "H. Felton" <fagricipni@gmail.com>
- Date: Mon, 6 Oct 2008 12:08:14 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=WCcLmOfZ/3PHD+ba45CdCiYl5b0oiK8913kFNwYCfKU=; b=E33kCbSutT/5+xLGNmzwe+QM/Zu+iJjehXBhM3iIbjTdLzJIi0wgTW87eRWFhThO17 GLasbwVr5klIL8MzLEOLJ5ArThkHb1hYHWC4CMkRBgA6eG9nG/r/sWmZ9DVsT1cBSF31 PxMIXKIKhZfWeoK+5+S495c4CClIm9zh3CsLQ=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=o0a+nGsDiVZCzTCfDmkZdIV5pVtpFqhgSM9c2UCnkM55MW0ddS22k1VcP1dwYi2f9u 1Mc+Cke3bae/JEjZ8L1SsNaZfr82yZrp061xQVKD/r3A2vD7WgFB82NzBuX8m2XB+UaM OEp3YQ9My0Cj/EYev0Vy5ohVtNucYO06t4xAY=
- In-reply-to: <48E7C137.8000100@scarlet.be>
- References: <E1KmAQz-0000w5-QJ@chain.digitalkingdom.org> <48E7AD62.4010307@finagle.org> <48E7C137.8000100@scarlet.be>
- Reply-to: lojban-beginners@lojban.org
- Sender: lojban-beginners-bounce@lojban.org
On 10/4/08, Killian De Volder <killian.de.volder@scarlet.be> wrote:
> Steve Sloan wrote:
> > > 2) What the computer does when the user presses it ("Apply", "Search")
> > >
> > > For 2), for instance, you can't just say "Sisku" on the button, as that
> > > (as
> > > I understand it) means "Look, a search/something searches!" which makes
> > > no
> > > sense in context. Would the button read "ko sisku" ("Hey you,
> > > Search!")?
> >
> > I think {sisku} would be fine, as most UI labels are already ambiguous as
> > to the actor. For example, "Get Mail" and "Print" are actions for the
> > application to perform, but "Write" and "Reply" are actions the user wants
> > to perform. You could add {ko}/{mi}, but that would probably just make
> > things more confusing: is {mi} the user, or the application?
So, "sisku" _can_ mean "ko sisku"?
If not, then the user interface dialog could end with "doi skami [ko
sisku] [ko basti]". The reason for not including the "doi skami" in
the button itself is so that it can reasonably apply to a list of
commands.
> How about omitting the mi / ko ? Making it unspecified, doing EXACTLY what
> you want:
> doing the same as what we read now in English, the short labels are
> ambiguous.
>
> I REALLY don't get the UI discussion issue.
> The complain is: it's not clear who the subject is ... aren't we trying to
> obtain that (ambiguously) ?
> And if you do want to show the actor, it's usually the program who is acting
> (so ko).
> A single "ok" choice je'e would be correct: "Yes I read the message you."
> But in case of a multi option je'e would be very confusing. (As Steve
> explained)