From: errno <errno@cox.net>
To: 9fans@9fans.net
Subject: Re: [9fans] crazy idea - drawterm in javascript?
Date: Tue, 17 May 2011 18:02:08 -0700 [thread overview]
Message-ID: <201105171802.08507.errno@cox.net> (raw)
In-Reply-To: <BANLkTi=cJZrMcPOOpamHt+HtaHVHSeEWxQ@mail.gmail.com>
Hey David, thanks for responding.
The sci-fi you write below is exactly the sort of fiction I'd find
very interesting in "9 space", and corresponds rather closely
to what I premised in a past thread[1].
So, I believe we're speaking the same language; but the picture
you've painted seems out-of-band to the drawterm-in-browser
idea presented by the OP; for instance:
> Instead of a "traditional web server platform" for web applications
> this could be an alternative deployment target.
>
If we're talking in terms of alternative deployment targets, then
we're talking about a controlled environment where we have
control over the installed software and hardware; but the
drawterm-in-javascript idea is intended for pre-deployed,
3rd-party accessibility to plan 9.
> Use a grid of Plan 9 machines with a "native" interface in JavaScript.
>
and:
> The one that doesn't look like a Plan 9 application, but instead looks
> like a useful application?
>
The drawterm-in-javascript-on-web-browser idea doesn't actually
provide a general-consumer-friendly interface to plan 9 - it just
amounts to window into the currently-existing plan 9 ui... we're still
talking text + libdraw, libpanel, libcontrol, libframe, etc..
I agree that an html + css + javascript ui on Plan 9 would be a
good and familiar way to get native Plan 9 applications into the
hands of general users; but this drawterm-in-javascript idea
does not facilitate the goal of a more "accessible/familiar"
WIMP environment for a general consumer market; though it
would be a useful tool once we finally did have a "native web"
within plan 9 itself, because then 'we' _could_ make good on
erik's:
> one would then be able to write applications for non-plan 9
> users in plan 9.
... in a way that would actually be appealing to non-plan 9
users.
[1] http://www.mail-archive.com/9fans@9fans.net/msg19990.html
next prev parent reply other threads:[~2011-05-18 1:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 7:00 Adrian Tritschler
2011-05-17 7:38 ` erik quanstrom
2011-05-17 15:02 ` Russ Cox
2011-05-17 13:59 ` Eric Van Hensbergen
2011-05-17 17:53 ` Joseph Stewart
2011-05-17 17:57 ` John Floren
2011-05-17 18:04 ` Joseph Stewart
2011-05-17 18:16 ` Jason Dreisbach
2011-05-17 18:00 ` Russ Cox
2011-05-17 15:08 ` Skip Tavakkolian
2011-05-17 17:23 ` Peter A. Cejchan
2011-05-17 17:31 ` John Floren
2011-05-17 18:18 ` erik quanstrom
2011-05-17 18:46 ` a z
2011-05-17 19:04 ` Skip Tavakkolian
2011-05-17 23:05 ` David Leimbach
2011-05-18 9:15 ` dorin bumbu
2011-05-18 9:40 ` a z
2011-05-17 22:49 ` errno
2011-05-17 23:40 ` Jacob Todd
2011-05-17 23:58 ` errno
2011-05-18 0:18 ` David Leimbach
2011-05-18 1:02 ` errno [this message]
2011-05-18 8:33 ` Balwinder S Dheeman
2011-05-18 9:49 ` Peter A. Cejchan
2011-05-18 12:24 ` blstuart
2011-05-18 14:23 ` David Leimbach
2011-05-18 15:37 ` Balwinder S Dheeman
2011-05-18 15:46 ` erik quanstrom
2011-05-20 12:41 ` Balwinder S Dheeman
2011-05-19 1:04 ` blstuart
2011-05-18 15:58 ` ComeauAt9Fans@gmail.com
2011-05-17 18:16 ` Skip Tavakkolian
2011-05-18 6:31 ` Peter A. Cejchan
2011-05-18 7:28 ` Charles Forsyth
2011-05-18 7:30 ` Peter A. Cejchan
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=201105171802.08507.errno@cox.net \
--to=errno@cox.net \
--cc=9fans@9fans.net \
/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).