Right now we can preview a link to another object and we have some choice over how that preview is displayed.
Let’s make it so that the preview can be fully expandable within the current document. For example, I have a note that contains a link to a list of book recommendations. From the preview I can see what exact it is and maybe small preview of what that “object” is whether a list/set, note, page, etc. ALmost like a window or a portal.
The user can then easily expand the object fully, within the currently open object. This could be done ad inifitium: If inside of the list of book recommendations, I have separate lists for fiction or nonfiction, in the note in which I’ve linked to the book list, I can full expand and edit the book list as though it’s the currently open object. I can then fully expand any objects within it, say I’m just interested in viewing the fiction books to add recommendation I heard, I can expand the books list object, then expand the fiction books object and add my recommendation
I think the preview interface that’s already integrated is the perfect building block. From there we allow the user to fully expand and edit that object from the preview pane.
There’s many ways to desribe this: portal, window, preview, etc. But I think portal is the most accurate. Window sounds nice but “wiindow” has already kinda been taken… by windows…
For portals to objects to be infinitely expandable - meaning one can have objects nested infinitely deeply yet view the entire contents of said objects from one frame/note, it would require a way to respect the page layout.
for example, if the preview is indented - that could make expanding the preview fully somewhat odd. The page may be a full fledged page and the indented preview would make restrict the width, which could lead to unexpected and undesirable behavior. Thus, if you’re going to make a fully expandable portal - it should be at the top level of the current object.
I also see a use case for example, a book list with two columns. Each column is actually a portal to a new list, one for fiction and one for non fiction.
In this case, in my main notes which I use to manage daily thoughts/tasks, I could make a portal to this book list, and from there, easily access and edit that object.
Already described above
currently, you can link to objects, and you can add previews to objects. More options regarding how to tdisplay those previews could be a good stepping stone
I believe there’s some over lap with Everything is a block and [nesting objects and sets inside each other(Nesting Objects/Sets inside each other - #7 by qualquertipo)
I think words like “nesting” have connotations of indentation and hierarchy which can derive from such indentations: 3 levels nested, that’s a grandchild etc.
I think the most simple and obvious wording is “embed” or “embedded portal” or “embedded object” I kinda lean towards using “embed” as a shorthand for “embedded object”. Portal just serves as a useful frame of reference as to what exactly is going on. But I also like using “portal” as a shorthand. I’m open to improvements of the nomenclature of course. Calling something a portal just has a more intuitive sense to it. Embed is more connotative of the means, and portal is more connotative of the ends. One way we could put it: A portal is simply an object which is embedded in another object.
I believe it will be necessary for the width of the portal, when fully expanded, to match that of the current document. That or to allow the user to define the layout of the portal. My reasoning for this being that the portal should be able to contain portals of its own. These portals should also be fully expandable, while staying in the context of the main note. The example of adding a book or movie recommendation comes to mind.
So how do we show this? How does the user know they’re looking at a portal within the context of the current note?
I have a couple ideas that I think could be really effective:
One point of these ideas and the idea of portals in general is to keep context. I believe that the “physical” metaphor really helps maintain context. The folks working on Stack Next for example, are doing a good job of showing that the closer to a physical representation we can get, the easier it is to reason about.
Instead of theorizing, I will describe a common use case and what that will look like:
I have a “main notes” which is just daily stuff. It’s like the central hub of my note taking (this is actually how I personally use my notes programs). Within Main Notes, I have a portal to my “Books recommendations” page. This page has a portal to two other pages: “Non fiction books” and “fiction books”
Within my main note, the “Books recommendation” portal looks similar to how a preview looks now. A layer atop the main note foundation. I click to expand the books portal and the preview expands to fill the full width of the page but maintains that feeling of sitting atop the main note. I then select to expand the nonfiction section. This too sits atop the books recommendation page and expands fully. From there I type in my recommendation and maybe some notes about why I am interested in this book.
I then collapse the books recommendation section.
The view maintains a physical metaphor by layering as opposed to a nested hierarchy.