does anyone know of any radical paradigms for navi...
# thinking-together
g
does anyone know of any radical paradigms for navigating the web? eg: not treating web pages like documents, not treating history as mostly ephemeral, facilitating collection or breadth-first search, weird zooming user interfaces, etc?
❤️ 1
a
Can’t find it in my notes any more, but I feel like one of the first ZUIs was a browser? When you clicked a link, the new page opened to the right and bigger. Hopefully there’s a lot in this area, that’s just what came to mind first.
g
that rings a distant bell for me, although i’m not sure i could google it
n
Some helpers: -Is HTML correct 'the one' which ties JS and CSS? What if the most first-class citizen would be pure data instead of ~GUI? (linked data stuff?) -How do you can use web hosted tools to work with content available from other sites (without manual integrations by either sites developer)? Example: why I cannot use CkEditor inline editor for arbitrary site like writing Slack comments?
d
You should look at Ted Nelson's book "Dream Machines" (1974). Nelson coined the word hypertext and invented the world wide web in the late 1960's/early 1970's. The web browser paradigm we use today was first implemented by Nelson and others as "The Hypertext Editing System" at Brown University, in the late 1960's. Nelson considered it a failed prototype, and went on to design a much better system, called Xanadu, which is documented in that book.
d
My own http://Object.Network design reinvents the web in a way: instead of HTML docs linked together, which assumes presentation level, with maybe some semantics piggy-backed on or tunnelled through, it has what I've unimaginatively called "objects" linked together. Like our familiar OO objects, these can be both data and docs, "semantic" or "model" as well as "view".
So, to more directly answer the OP's challenge: in the Object Net you can navigate through the network (web) of objects by transclusion or by jumping to linked objects, just like in the web. So the interface is a 2D view of nested boxes each representing an object you can see from the current object you're on, via links, up to a finite depth. So for example you get the "mirrors facing each other" effect if two objects point to each other and you keep opening each up inside the other.
If an object happens to be a "view" or document or presentational object that the "browser" recognises, it can be rendered as the fully painted thing, not the raw data.
d
Check out rebl by Cognitect
g
love rebl, and i actually own a hard copy of dream machines haha. more curious about practically drawn out examples, eg https://www.mercuryos.com/ but for just networked data. i think this is my kick in the pants to finally dig into onex
d
Mercury would be a perfect UI for Onex. I may steal all their ideas. 😄
❤️ 1
Onex doesn't have apps either. Each Module in Mercury corresponds to an object or view/model object pair in Onex.
@Garth Goldwater ↑↑
g
the other UIs that strike me as relevant if you find that interesting are exactly:
rebl:

https://youtu.be/c52QhiXsmyI

and moldable development with gtoolkit:

https://youtu.be/Pot9GnHFOVU

if you’re looking for more inspiration
d
Oh thanks, Garth 😄
s
See also Ted Nelson explain his work in this series:

https://www.youtube.com/watch?v=hMKy52Intac&list=PL_VPHE35-pxem4YDQVsvfdlxu1lLZXGDW

👍🏼 4