9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: blstuart@bellsouth.net
To: 9fans@9fans.net
Subject: Re: [9fans] more little hardware
Date: Tue, 16 Mar 2010 11:33:15 -0500	[thread overview]
Message-ID: <0031345be9b30320af24b9f8f7df69a7@bellsouth.net> (raw)
In-Reply-To: <6e35c0621003161010w1f35b4e4jacff800457ac5252@mail.gmail.com>

>> I was wondering how you'd network one of those things:
>>
>> http://en.qi-hardware.com/wiki/Wi-Fi_in_Nanonote

I thought that was terribly cute.  The other option is talking
PPP over the USB.  You'd be tethered, but you could at least
talk.

> Off-topic-ish, that 320x240 screen is probably the biggest challenge,
> trying to find some usable UI in that space. I think the idea of a
> native Inferno port is great. Anyone doing anything fun on the UI side
> with the Nintendo DS port?

Yeah, that's what I was figuring too.  Even at a 5x7 font, you can't
do better than about a 50x30 character screen.  If all the graphical
elements in wm are shrunk down to somewhere around 10 pixels,
it might just be possible to put a shell window that's almost usable.
Acme in a single column might even work.  Of course, I'd really
like to have more resolution, but this is a start and who knows
what we might see in a second generation.

BLS




  reply	other threads:[~2010-03-16 16:33 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 10:34 maht
2010-03-16 14:54 ` blstuart
2010-03-16 16:44   ` John Floren
2010-03-16 16:17     ` blstuart
2010-03-16 19:35     ` Tim Newsham
2010-03-16 19:46       ` John Floren
2010-03-17  4:03         ` Tim Newsham
2010-03-17  4:50           ` ron minnich
2010-03-17 14:38             ` David Leimbach
2010-03-18  6:59             ` Tim Newsham
2010-03-18  8:04               ` Steve Simon
2010-03-18  9:24                 ` Gabriel Díaz
2010-03-18 14:36                   ` David Leimbach
2010-03-18 15:42                     ` Jorden Mauro
2010-03-24 22:28                       ` Jack Johnson
2010-03-28 14:33                         ` Georg Lehner
2010-03-18 12:46                 ` erik quanstrom
2010-03-18 14:27                   ` Patrick Kelly
2010-03-16 21:02     ` Patrick Kelly
2010-03-16 23:38       ` ron minnich
2010-03-16 23:47         ` Patrick Kelly
2010-03-17  9:05         ` Charles Forsyth
2010-03-17 14:02           ` Stuart Morrow
2010-03-17  9:35         ` hugh
2010-03-17 15:08           ` ron minnich
2010-03-17  2:05       ` David Arnold
2010-03-17 11:11     ` maht
2010-03-17 13:57     ` Stuart Morrow
2010-03-17 18:06       ` Jack Johnson
2010-03-17 19:13         ` John Floren
2010-03-17 19:49           ` Axel Belinfante
2010-03-17 19:57             ` Axel Belinfante
2010-03-17 20:11               ` John Floren
2010-03-18  6:53         ` Tim Newsham
2010-03-16 16:53   ` Jack Johnson
2010-03-16 17:10     ` Jack Johnson
2010-03-16 16:33       ` blstuart [this message]
2010-03-16 18:20         ` ron minnich
2010-03-16 19:24           ` blstuart
2010-03-16 17:12       ` Jack Johnson
2010-03-16 17:52 Jonas Amoson
2010-03-16 17:24 ` blstuart

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=0031345be9b30320af24b9f8f7df69a7@bellsouth.net \
    --to=blstuart@bellsouth.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).