9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Willow Liquorice <willow@howhill.com>
To: 9front@9front.org
Subject: [9front] Musings on web browsers and office applications
Date: Mon, 1 Apr 2024 03:13:38 +0100	[thread overview]
Message-ID: <9a2ec537-c6a5-4c44-8306-d12ebee98446@howhill.com> (raw)

Hi,

I've had Plan 9 on the brain for the past few months, and I read a pdffs 
in the recent conference proceedings, and I was wondering whether the 
principles in that paper could be applied to create a file server for 
something that uses the Document Object Model.

You could then use the resulting directory tree in the core of a web 
browser (HTML) or office application (OpenDocument / Office Open XML).

Just off the top of my head, maybe an example HTML document could be 
represented like this?

html/
   !attrs/
     lang
       "en"
   01 head/
     01 title/
       01 text
	"Test Page"
   02 body/
     01 p/
       !attrs/
	class
	  "dumb-stuff"
       01 text
	"according to all known laws of aviation"
       02 comment
	"why are you doing this"
       03 em/
	01 text
	  "there is no way that a bee should be able to fly"
       04 comment
	"please stop"

Consider "text in quotes" to be the contents of the files they appear 
under.

I think the scheme above would work to identify attributes: the 
directory name would simply be an invalid tag name.

What do you think? I don't know that much about 9P, so maybe there's a 
better way of expressing the order of elements in a directory tree than 
literally numbering the files and folders.

	- Willow

             reply	other threads:[~2024-04-01  2:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01  2:13 Willow Liquorice [this message]
2024-04-01  9:17 ` Pavel Renev
2024-04-03 20:42   ` Willow Liquorice
2024-04-04  2:23     ` an2qzavok

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=9a2ec537-c6a5-4c44-8306-d12ebee98446@howhill.com \
    --to=willow@howhill.com \
    --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).