9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Randolph Fritz <randolph@cyber-dyne.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] gtk port
Date: Thu, 29 Jun 2000 22:08:51 -0700	[thread overview]
Message-ID: <20000629220850.A8523@cyber-dyne.com> (raw)
In-Reply-To: <20000630010106.11410.qmail@ken.aichi-u.ac.jp>; from arisawa@ar.aichi-u.ac.jp on Thu, Jun 29, 2000 at 08:57:02PM -0400

On Thu, Jun 29, 2000 at 08:57:02PM -0400, arisawa@ar.aichi-u.ac.jp wrote:
>
> Recent web pages are full of noisy commercials and junk images.
> Therefore it may be a good idea to have a brawser based mainly
> on text providing ability to get images in case of necessity.
> Then the ideas:
> >   echo 'http://www.sciencemag.org/' > /mnt/web/get
> >   cat /mnt/web/data
> or
> >   cat /http/www.sciencemag.org
> or some other operations like plumb may be nice for plan 9.
>

It depends...as an architecture student & photographer I deal in
graphics, and many sites of architectural firms would simply not be
usable without them--take a look at
<http://www.fosterandpartners.com>, for instance.  Even for more
conventionally-designed sites, a little bit of layout often makes all
the difference between clarity and obscurity--I use lynx sometimes,
but I don't enjoy it. :(

Perhaps the thing to do is port Mozilla's NGLayout (aka Gecko (tm)*)
HTML/XML rendering engine, and see what support it needs--most of the
graphic components are already there, and Plan 9's graphics model has
one excellent advantage over Windows and MacOS--it already does
transparency, which CSS requires.  Plan 9's distributed design might
be well-suited to a modular browser; that might even become a popular
app.

--
Randolph Fritz
Eugene, Oregon, USA

* Gecko is a trademark of Netscape, Inc. :)


  reply	other threads:[~2000-06-30  5:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-30  0:57 arisawa
2000-06-30  5:08 ` Randolph Fritz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-30 14:45 bwc
2000-06-30 22:02 ` arisawa
2000-06-30 12:24 rog
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
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

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=20000629220850.A8523@cyber-dyne.com \
    --to=randolph@cyber-dyne.com \
    --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).