From: Marshall Conover <marzhall.o@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Re: Plan 9 applying to GSoC
Date: Sat, 19 Feb 2022 12:18:26 -0500 [thread overview]
Message-ID: <CAK0pxsG_2oDOC0-coyCKNahnO31Z1MNszXxRs6FhZkWot_qHtQ@mail.gmail.com> (raw)
In-Reply-To: <8635keal1r.fsf@cmarib.ramside>
[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]
Adding a +1 for sirjofri's idea 3, which seems like it would be achievable,
has clear objectives, and a compelling result.
For idea 4, a notable utility is pipefile -
https://9p.io/magic/man2html/1/pipefile. It allows you to stitch a command
in-between the reading and/or writing of a file. It'd be worth eyeballing
and considering for the purposes you're thinking of, and may provide a
jumping-off point.
Cheers,
Marshall
On Sat, Feb 19, 2022 at 11:33 AM <cigar562hfsp952fans@icebubble.org> wrote:
> sirjofri <sirjofri+ml-9fans@sirjofri.de> writes:
>
> > (3) A high-level filesystem interface for UI widgets. Many modern UI
> > layouts can be described as a hierarchy of containers. The UI
> > filesystem would start as an empty window, which is reflected by an
> > empty filesystem. The user could create widget containers (hbox, vbox)
> > by creating directories and files, as well as input boxes, buttons and
> > more by creating files. The hierarchy would directly reflect the drawn
> > window. The user can listen to files for button interaction and write
> > text to labels etc..
>
> Ballastero(sp?) and lsub's Octopus (Omero? O-something) does something
> like this. With it, you can tar/untar a Tk UI from one system to
> another. IIRC, it was implemented with Inferno. Since I is similiar to
> 9, it probably wouldn't be too hard to port.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Td4449edc4863e16e-M709844316c73d6efec7d190b
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 3169 bytes --]
next prev parent reply other threads:[~2022-02-19 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 20:03 [9fans] " Anthony Sorace
2022-02-18 22:43 ` [9fans] " adventuresin9
2022-02-19 0:19 ` hiro
2022-02-19 3:56 ` adventuresin9
2022-02-19 10:21 ` [9fans] " Lucio De Re
2022-02-19 11:00 ` sirjofri
2022-02-19 16:16 ` [9fans] " cigar562hfsp952fans
2022-02-19 17:18 ` Marshall Conover [this message]
2022-02-19 18:06 ` [9fans] Omero/UI filesystem (was: Plan 9 applying to GSoC) sirjofri
2022-02-20 17:45 ` [9fans] Plan 9 applying to GSoC ori
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=CAK0pxsG_2oDOC0-coyCKNahnO31Z1MNszXxRs6FhZkWot_qHtQ@mail.gmail.com \
--to=marzhall.o@gmail.com \
--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).