Maybe now when I shared Literature Review with Tinderbox document, it should be easier for me to explain what I had in my mind.
In that project, there are three prototypes (nodes) and three kinds of link types (relationships when we add direction) that are fundamental for the synthesis process and create the grammar of my discourse graph. But that’s a grammar that is useful to me, but for somebody else it should contain more/fewer nodes and different kind of relationships. To make it easier for others to switch between different grammar patterns, I would like to create a container note (‘Nodes’) with nodes inside it and let them set relationships between those nodes by simple linking between them. $Edict inside ‘Nodes’ would watch children notes and, based on created nodes and relationships, automatically add action code to individual link types. I hope it makes sense, and you can understand what I mean.
I have to agree that’s a pretty niche use, and I’m uncertain if it is worth from a ROI perspective - I’m not a software developer myself, nor I have much knowledge of other TBX user use cases.
The other thing I think would be useful, but maybe easier to implement, is to let the user be able to get information about link details from Browse Links pop-over.
Sometimes short description (Link Type name) is not enough to describe why I linked one note with the other, that’s why I put some description in Browse Links pop-over. What’s problematic is to get back this information, especially when you have dozens or hundreds of notes linked to each other. What I propose is action code scheme like this:
linkDetail(sourceDesignator,destinationDesignator[,linkType])With this action code, one could still use Browse Links pop-over to write down some detailed information about the link, and easily get this information back when exporting notes.
Arek