From: cigar562hfsp952fans@icebubble.org
To: 9fans <9fans@9fans.net>
Subject: [9fans] Re: Plan 9 applying to GSoC
Date: Sat, 19 Feb 2022 16:16:48 +0000 [thread overview]
Message-ID: <8635keal1r.fsf@cmarib.ramside> (raw)
In-Reply-To: <98804c9e-140d-4a3f-9446-bc5c152119ba@sirjofri.de> (sirjofri's message of "Sat, 19 Feb 2022 11:00:37 +0000 (UTC)")
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-Mc494dd5ad027aad6fc42c2fb
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-02-19 16:32 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 ` cigar562hfsp952fans [this message]
2022-02-19 17:18 ` [9fans] " Marshall Conover
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=8635keal1r.fsf@cmarib.ramside \
--to=cigar562hfsp952fans@icebubble.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).