9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9fans@sirjofri.de>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Omero/UI filesystem (was: Plan 9 applying to GSoC)
Date: Sat, 19 Feb 2022 18:06:35 +0000 (UTC)	[thread overview]
Message-ID: <9d91ab77-997b-4449-8728-768de8b18fb2@sirjofri.de> (raw)
In-Reply-To: <CAK0pxsG_2oDOC0-coyCKNahnO31Z1MNszXxRs6FhZkWot_qHtQ@mail.gmail.com>

Hello you two,

yes, others in the community also pointed me towards Omero and I skimmed 
through the man page about it. I don't know much about Plan B/Octopus, 
but it seems the general idea is very similar to what I have in mind.

However (you can correct me if I'm wrong), it seems that it is tailored 
to the Plan B UI, which looks very different to the standard devdraw/rio 
way of doing UI, so I guess there's quite some work to do.

For people who are interested: I played around with the concept some time 
ago, but I wasn't good at writing filesystems back then. The solution I 
came up with was rcgui, which is not a full filesystem but just a 
connection (as a pipe) with a textual interface. 
https://git.sr.ht/~sirjofri/rcgui

In general, I believe that with solid native filesystems and solid native 
programs many applications can just be shell scripting "glue" between the 
(descriptive) UI layer and the backend filesystem. For more complex 
applications devs might want to use the native programming language to 
write this "glue" or even make it part of the native backend application.

One component-based descriptive UI filesystem would open this gate for 
both approaches and UI designers can mockup their designs very easily.

Plan 9 is often about abstracting resources as filesystems, and I believe 
UI shouldn't be an exception. Devdraw abstracts drawing already, but I 
think the common way of making/managing/controlling UI can be abstracted, 
too.

sirjofri

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T765c829f434b0f6f-Me7af5b7e4822047d9bdf27b3
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2022-02-19 18:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 20:03 [9fans] Plan 9 applying to GSoC 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
2022-02-19 18:06       ` sirjofri [this message]
2022-02-20 17:45 ` [9fans] " 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=9d91ab77-997b-4449-8728-768de8b18fb2@sirjofri.de \
    --to=sirjofri+ml-9fans@sirjofri.de \
    --cc=9fans@9fans.net \
    --subject='Re: [9fans] Omero/UI filesystem (was: Plan 9 applying to GSoC)' \
    /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

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).