![]() I’m using templates to create a structure with a mix of 1-column and 2-column relation lists. But that’s not very readable or practical. Today the few layout options allow at best to show a row of selected relations in the object detail view. I believe the solution could be in layouts rather than templates. That is, click on an object and see all its relevant relations (switching to Anytype talk now) in a readable and editable way. I think that what we often (though, granted, not always) will be looking for is a way to create/maintain a nice “properties view” to speak in Notion terms. Having read the discussion, and thought about the differences between AnyType and notion, I wonder if t he core need of 80% of people in this situation can be reframed in a way that allows for technically (and conceptually) easier solutions. As many other people in this thread I quickly felt the need to maintain a template linked with a type after objects of that type were created already, and see the template changes applied. I’m new to AnyType, coming mainly from Notion. any existing object that isn’t attached to a template can be attached to one: in this case, it will lose its existing relations and gained all of the templates’ relations.if you don’t want an object to follow a particular template anymore, simply “detach” it.update a template, and all attached objects will get the update.create an object from a template, and that object is automatically “attached” to that template: the object has all the relations from the template.To implement this, the only change needed would be the ability to “attach” and “detach” objects from templates: In Anytype, instead of applying to all objects in a Collection (the equivalent of applying to all pages in a Notion database), this process could be tied to entire types or specific templates: add, edit, or remove a relation in a template, and all of the objects that follow that template will see their relation updated. This is basically the same as changing properties in a Notion database: add, remove, or edit a property in the database, and all of the pages in the database will get the update. To me, the most important and urgent aspect of this is to bulk-update relations. ![]() I think nails it on the head: Option to apply template to an existing object - #58 by Shampra And there you go: if the template evolves, the modification of the template can be automatically applied to all objects with that template!" The template defines how it’s presented, adding editable “fields” through the insertion of relation. One (among other) possibility would be a form mode: the object can’t be modified outside the relationships! A sort of form, in a way. And it addresses some requests mentioned above.Īpplying the modifications to the page is more complicated as it can be altered in all directions! This one would be to apply bulk addition/removal of relations and Featured Relations (for all objects with the template).ĭevelopment-wise, I don’t see complications, it’s outside the modifiable parts of the objects (even if we add relations to only one of the objects, there’s no problem in removing the initial ones or adding new ones, and no problem marking them as featured). This FR can be divided, with a simpler FR that allows us to start addressing a portion of the needs. But anticipated! From the discussion, two things emerge: ![]() ![]() After discussing with a future convert (hopefully), this point is really anticipated.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |