Agree. I’ve suggested before (link below) that everything should be an object - this would include paragraphs/blocks within a “page”, and even Relations.
I don’t think I mention Titles, but I also think they should be an Object as any other, and therefore capable of containing inline references (and anything else an Object/Block can contain).
Haven’t seen your feature request. The everything is an object approach would be very nice. I assume that adding an inline object to the title would be an interim step towards this goal.
I would be very curious to see what the Anytype team thinks of this discussion. I very much agree that everything should be an Object, including titles (= object name?) and descriptions.
Everything is an object is a nice metaphor but to threat title as an object is a hyperbolization for my taste. Everything inside the canvas is a block for now, even a relation or link to another object.
As far as I understand the original request is to add possibility to mention in the title of page. Am I right?
Another way to see this is that the Title is just a block like any other, parent to all blocks within it.
Have you guys checked out RemNote? It does this very well. The result is a structure that on the surface functions like a traditional page-based system for the casual user, but with enormous potential for granularity and more advanced applications for the more adventurous users.
I appreciate that AT has its own thing going on, of course. Just food for thought!
I vote for this. I use this in Notion all the time, as in “Call @Joe”, which allows me to both click through to Joe and to see on Joe that he’s referenced.
This seems like mostly an oversight?
Also, this could be considered a bug:
If I have a note and type “Call @Joe” as the first line, then change the layout to Action / Task, then the first line becomes the title / name and the reference is lost.
Titles of objects should be able to contain links to other objects.
HOW COULD IT BE DONE
The usual @-notation will work, so that links can be added the same way as in any other text area. When the object title is displayed as itself (not as a link), then the links within it should be underlined and followable as normal. When the title is displayed as a link to its object, then links within it should be ignored. Because of this latter behavior, nested links will not cause trouble.
REAL WORLD USE CASES
I sometimes need the title of one object to contain a link to another object. This is because the text of links to an object is updated when the title of that object is updated. When the title of one of my objects A includes the title of another object B, there’s no way for me to establish that link so that the title of A will be automatically updated if the title of B is updated.
Probably this feature should only be implemented if it happens to be a low-hanging fruit. Otherwise it would make more sense to make this possible as part of a broader computed-relation effort. The values of relations should be computable from the values of other relations, perhaps on other objects. No reason for titles not to be included in this.
RECOMMENDED ALTERNATIVES
Right now I use a system of manual reference tracking. I made an object reference relation “Title referrers”, which I use to store references to all other objects that use the object’s title in their own title. But as you can imagine this is tedious and, when an object’s title is popular in other titles, potentially time-intensive to update.
I support this feature request. I am in a process of migration of more than 10.000 documents from Zim to Anytype. Since Anytype doesn’t support nested hierarchical documents, a structure of pages and sub-pages changes during import into a large amount of equal documents in a flat structure. Since flat structure doesn’t work well with thousands of equal documents (their graph is very slowly rendered and very disarranged), I am forced to merge many nested sub-pages into their parents, so the result is a small amount of very large documents, divided into many sections and subsections, with a very long table of contents. For this reason section linking is a very important feature.
Looks like this feature request is the same to the following request, except it does not specify to using @. Trying searching on the forum before you need to write the whole thing up, it saves you time for more new feature request .
It’s not quite what I’m asking for, since it will require the user to first place the object they want to link to into a relation on the object. Which is cool in itself, but my FR wants to be able to add the link directly in the title, not get the link indirectly by referring to a relation which then refers to the target object. The two can be used to achieve identical effects, but the other FR can do things above and beyond what I’m asking for at the cost of additional mouseclicks and keypresses. And those extra interactions I want to avoid, because they’ll slow me down. And also I don’t want to create relations “Title link 1”, “Title link 2”, “Title link N”, when my title needs to link to multiple other objects.
@ is definitely a quick way to link objects, no matter if it is adding to blocks or titles.
Most likely ‘Link in title’ is easier to implement compared to ‘title from relation’.
But perhaps the reason why I find it the same is the logic behind such implementation.
Treat Title as block
Make connection from title
Thus, I thought it might be sparkle more discussions if we consider both together.
Yeah, that one does seem close enough to me. It doesn’t mention @-notation, but I’ll just make a reply there adding it. I didn’t find it because it uses the words “reference” and “name”, when I searched for “link” and “title”. Ah well.
I think this means this entire topic can be safely deleted without any loss to the conversation.