From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] nix at lsub
Date: Wed, 18 Apr 2012 14:35:41 +0200 [thread overview]
Message-ID: <0A67293D-C709-4332-9EDE-3C2CB8EB9B35@lsub.org> (raw)
In-Reply-To: <CAOw7k5jLKO4AP97ek-JoYqzzoc70i8bhT7k3EgBSjyenZOxeZA@mail.gmail.com>
To make it explicit, the plan I have is to
throw away o/live and o/mero and write something native for
macos, linux, and perhaps ios such that the UI widgets are abstract
and handled in a similar way they are handled in o/live.
Only that they'd be native widgets with the look of the native system
(that's not to say you can't implement an editable text-pannel with
the mouse language we all love).
Also, as Forsyth points out, the set of widgets has to be rethought, e.g.,
there should be a web widget.
Then it's a matter of using those files from inferno, and remote systems.
But, as I said, I don't have a single line of code yet for all of this.
On Apr 18, 2012, at 2:27 PM, Charles Forsyth wrote:
> I should add that "along the lines" of Octopus meant that,
> as often happens, many of the details might change to account
> for experience and second thoughts, and for changed technology.
> Obvious candidates for the latter would be the increased availability of 3D,
> and vastly greater browser capabilities (for good or ill).
>
next prev parent reply other threads:[~2012-04-18 12:35 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 21:02 Nemo
2012-04-15 13:45 ` David Leimbach
2012-04-16 10:47 ` Francisco J Ballesteros
2012-04-16 11:02 ` Noah Evans
2012-04-16 17:23 ` Aram Hăvărneanu
2012-04-16 17:32 ` Noah Evans
2012-04-16 17:42 ` Noah Evans
2012-04-16 17:44 ` ron minnich
2012-04-16 20:53 ` Andrés Domínguez
[not found] ` <CAEAzY380ECzLQJCbNaK=QiYE6vzQpqTW3ZoakzW7EJ-WajptHg@mail.gmail.c>
2012-04-16 17:54 ` sl
2012-04-16 13:22 ` Christoph Lohmann
2012-04-16 18:04 ` Lucio De Re
2012-04-17 2:16 ` kokamoto
2012-04-17 5:53 ` andy zerger
2012-04-17 5:54 ` andy zerger
2012-04-17 7:17 ` Nemo
2012-04-17 8:41 ` kokamoto
2012-04-17 8:51 ` Francisco J Ballesteros
2012-04-17 12:22 ` Tristan
2012-04-17 18:56 ` Charles Forsyth
2012-04-17 19:13 ` Nemo
[not found] ` <charles.forsyth@gmail.com>
2012-04-18 0:26 ` kokamoto
2012-04-18 4:07 ` John Floren
2012-04-18 4:12 ` John Floren
2012-04-18 7:54 ` Francisco J Ballesteros
2012-04-18 12:27 ` Charles Forsyth
2012-04-18 12:35 ` Francisco J Ballesteros [this message]
2012-04-18 15:45 arnold
2012-04-18 15:49 ` Francisco J Ballesteros
2012-04-18 16:09 arnold
2012-04-18 16:18 ` Nemo
2012-04-18 16:28 ` Charles Forsyth
2012-04-18 16:35 ` Francisco J Ballesteros
2012-04-18 17:43 ` Lucio De Re
2012-04-18 18:05 arnold
2012-04-19 1:37 ` hiro
2012-04-19 4:15 ` Jeff Sickel
2012-04-19 8:10 ` Charles Forsyth
2012-04-19 8:16 ` Joseph Stewart
2012-04-19 8:46 ` Charles Forsyth
2012-04-19 10:03 ` Bakul Shah
2012-04-19 10:32 ` Charles Forsyth
2012-04-19 16:36 ` Bakul Shah
2012-04-19 15:50 ` ComeauAt9Fans@gmail.com
2012-04-19 16:11 ` Lucio De Re
2012-04-19 17:09 ` ComeauAt9Fans@gmail.com
2012-04-19 17:56 ` Lucio De Re
2012-04-19 18:05 ` Comeau At9Fans
2012-04-19 18:23 ` Lucio De Re
2012-04-19 18:27 ` Lucio De Re
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=0A67293D-C709-4332-9EDE-3C2CB8EB9B35@lsub.org \
--to=nemo@lsub.org \
--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).