From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] 9front on the Allwinner A64
Date: Tue, 29 Nov 2022 09:04:01 +0100 (GMT+01:00) [thread overview]
Message-ID: <ccda768f-67e2-4560-9b5b-395b8d253f4f@sirjofri.de> (raw)
In-Reply-To: <Y4U535YLKPRrARi6@wopr>
Hello,
I think you guys don't fully understand what I plan to do, UI-wise.
I want a pure Plan 9 phone. This doesn't mean I want an adjusted rio and a way to do mouse clicks to fulfill the expectations of what Plan 9 intended for a desktop UI with a mouse and keyboard.
This means, I want to design a fully new UI system that matches the philosophical expectation of "Plan 9", whatever this means. It's not a definitive concept yet, although I have a few ideas that I want to test out (and bitsy/keyboard will be used as a starter).
The goal is to have a Plan 9 device that really feels like a Plan 9 phone, but with a natural way to interact with the system.
Of course I could just copy smartphone UI stuff from Android (or iOS), but you'll soon feel that it's not a Plan 9 system at all. It'd merely be a "modern" UI with a Plan 9 kernel under the hood, much like you don't feel a linux under Android although it is there.
I want the system to be so Plan 9-ey that you can feel Plan 9 each time you use it. I want the system to be fun in a way that you _want_ to use it. I want the system to be productive so that you _can_ use it. And finally (maybe not finally) I want the system so that you can use it within your bigger context of a Plan 9 grid[1].
It should feel natural to interact with existing backend system components like the plumber. In fact, Android has a similar system with its intents, but I can't just copy that and make it work with plumber; it would never feel right. I have to go back to the roots of Plan 9 UI development and design a new system from the ground up, that feels as natural as clicking with a mouse inside acme or using the context menu to send data to the plumber.
I know this is a big challenge and is definitely worth a paper. I wish I had more time to prepare design documentation and concept descriptions for you. The good thing is, I can very likely start developing (and testing, to some extent) on a Plan 9 system on a computer.
sirjofri
[1] This means, you can naturally access your phone from any grid device et vice versa. So you can basically rcpu into your phone and do phone calls.
next prev parent reply other threads:[~2022-11-29 8:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 19:45 sirjofri
2022-11-28 0:26 ` adventures in9
2022-11-28 7:56 ` sirjofri
2022-11-28 21:06 ` adventures in9
2022-11-28 21:20 ` unobe
2022-11-28 22:44 ` Kurt H Maier
2022-11-29 8:04 ` sirjofri [this message]
2022-11-29 14:42 ` Kurt H Maier
2022-11-29 16:50 ` sirjofri
2022-11-29 18:04 ` Tom Schwindl
2022-11-29 18:59 ` adventures in9
2022-11-29 19:23 ` Tom Schwindl
2022-11-30 2:38 ` Stuart Morrow
2022-11-30 6:34 ` adventures in9
2022-12-01 14:12 ` Stuart Morrow
2022-11-30 2:35 ` Stuart Morrow
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=ccda768f-67e2-4560-9b5b-395b8d253f4f@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--cc=9front@9front.org \
/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).