9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Artem 'Thomas' Hlushko" <tom@topspin.kiev.ua>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] gtk port
Date: Fri, 30 Jun 2000 08:24:55 +0000	[thread overview]
Message-ID: <962304496.164232@jet.ncc.icyb.kiev.ua> (raw)
In-Reply-To: <lzowvj8fzvg.fsf@migi.aist-nara.ac.jp>

Hiroki Tamakoshi <hiroki-t@is.aist-nara.ac.jp> wrote:
> Hello,

> Why do you think that is a bad idea?
because this is not plan9 way (see plan9.bell-labs.com/sys/doc/*)

> Why do you push tcl/tk?
because this is better approach in computer system design.
there is power not only in graphics capabilities of tk,
but in philosophy of tcl. systems are made of 'hard'
pieses in c and etc by gluing with tcl and pipes.
it is very close to real unix way (see upe by bwk&pike)

> It is not the problem to choose gtk or tcl/tk.
> My opinion is, from the point of view of the Human-Computer
> Interaction, that Plan 9 should have a potential to establish a good
> GUI for end users. Off course, there could be another solusion than
there are popular oses with drag'n'drop, point'n'click, popup menus'n'windows
they are used by housekeepers, clerks, sales managers and gamers.
but why do so many people think this is only way?
why Human-Computer Interface should be same for nuclear plant operator
or airport dispetcher and for sales manager or housekeeper?

i think plan9 is intended for cs researches, scientists in another fields,
mission-critical applications experts and so. they are primary
interact with computer by program it, order it and ask it.
sometimes they browse web, look at experimental data
and read ps/pdf/dvi then they need graphics interface.
good Human-Computer Interaction for them is close to plan9 one
and is far to gnome.

> porting gtk.
> (and even if porting gtk fail, porting glib is worthwhile, because
> glib is a very useful library.)
plan9 libc very useful too...

at least i don't think tcl/tk very need in plan9
you can create server with filesystem interface
or add some graphical capabilities in rc :)))

there is not only one way to compute!


  reply	other threads:[~2000-06-30  8:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-28 18:04 Hiroki Tamakoshi
2000-06-29 10:56 ` Artem 'Thomas' Hlushko
2000-06-29 12:14   ` Hiroki Tamakoshi
2000-06-30  8:24     ` Artem 'Thomas' Hlushko [this message]
2000-06-30 10:15       ` Hiroki Tamakoshi
2000-06-30 13:35         ` Artem 'Thomas' Hlushko
2000-07-01  3:32           ` Berry Kercheval
2000-07-03  9:34             ` Dennis Ritchie
2000-06-30 14:28         ` Randolph Fritz
2000-07-03  9:36           ` Douglas A. Gwyn
2000-06-29 12:52   ` Wladimir Mutel
2000-06-29 21:44     ` arisawa
2000-06-29 22:02     ` James A. Robinson
2000-06-29 22:51       ` Randolph Fritz
2000-06-30  2:18         ` Skip Tavakkolian
2000-06-30  1:41           ` Jim Choate
2000-06-30  3:02           ` arisawa
2000-06-30  1:33       ` James A. Robinson
2000-06-30  5:13         ` Randolph Fritz
2000-07-03  9:34           ` Andy Newman
2000-06-30  6:03         ` James A. Robinson
2000-06-30  8:26         ` Jonathan Sergent
2000-06-30  0:57 arisawa
2000-06-30  5:08 ` Randolph Fritz
2000-06-30 12:24 rog
2000-06-30 14:45 bwc
2000-06-30 22:02 ` arisawa

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=962304496.164232@jet.ncc.icyb.kiev.ua \
    --to=tom@topspin.kiev.ua \
    --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).