We create a new Entity View where per-Type elements (rich-text Fields → Text Blocks, context Lists → View Blocks, etc.) coexist with per-Entity elements (Text/Whiteboard/View Block). Structured Fields (currently on the right) are left intact for now. No need to migrate EVERYTHING on the left (File…

As for the “RichEdit text” blocks, there is such a thought (since you are moving to the new block model anyway :innocent: ) — Add versioning (history) at the block level. For some reason, Roam Research does not mention this function in its help and does not emphasize it. But in my opinion, it is fr…

[image] rothnic: Is the helper intro text and text after the view in my described use case separate rich text fields? In other words, would we have to add rich text fields each time we want to add a paragraph between two views that have been embedded as blocks? I know Michael addressed this,…

[image] Oshyan: Take a closer look at the mockup, there is a history button on each block already. Assuming the mockup is accurate, it seems they are already planning this. :slight_smile: The main question here is, in what form will it be? :grinning: “Standard version history” or “The abilit…

[image] Oshyan: I know Michael addressed this, but in case there is remaining confusion, my understanding is that Blocks will be arbitrary units of content/functionality, and will not have to be consistent from entity to entity, thus they do not involve creating “fields”. They are a more “lightw…

[image] a2say: Add versioning (history) at the block level. It is a side-effect of our implementation :slight_smile: Every large text block is a rich edit text with its own history.

[image] Oshyan: I would also really love to see “in-line calculated values” like Coda and a couple other tools can do This will be easy to add I hope, we’ll definitely consider it.

[image] a2say: “Standard version history” or “The ability to save a block variant in manual mode. And a convenient comparison of these variants”. Ahh, I see, you specifically want named versions. Well, this feature doesn’t exist in Fibery yet, but has been requested . And based on what Michael…

[image] Oshyan: Can you clarify what you mean by “large” text block? This is where my confusion came in. I’m aware that each rich text field and document is a separate prosemirror document, which allows the fibery team to support collaborative editing, etc without building it out on their own…

Yes, you are exactly right. My explanation was not clear since I didn’t share enough context. Sorry for that!

[image] rothnic: So, to answer your question, it sounds like all text and embedded items you add to a rich text block when you click “+ block” would be a single unit of content. You could write a single word or a novel in that block and fibery will treat it as a single chunk of content. Each lin…

Migrate Entity View to Blocks

Ideas & Features

mdubakov October 11, 2021, 2:10pm 13

This will be easy to add I hope, we’ll definitely consider it.

Block inputs and outputs

Use data or table functions inside a document

Google Sheets Integration

Topic		Replies	Views
[DONE] Embed Custom Views into Entity View Ideas & Features blocks	18	4573	August 18, 2022
Show in Reference Highlights Referenced Entity more clearly Ideas & Features blocks	13	1441	November 9, 2021
References to Views as a way to emulate Embedded Db's in Notion Ideas & Features	22	4786	June 15, 2021
We've improved Docs greatly this year. Do you still REALLY miss something? News & Announcements	48	3500	January 26, 2024
In Highlights, "Roam-like" inclusion of Hierarchy of Text Blocks Ideas & Features	11	2063	November 12, 2020

Migrate Entity View to Blocks

Related topics