As soon as we released Hookmark 1.0 in beta, we received several requests for a more visual representation of the links managed by Hookmark. (For example, this post in February 2019, the month we released Hookmark beta.)
Here’s a conceptual schema of a network graph view.
We would like to gauge the interest in a visual representation of the links in Hookmark. A initial version of this would be a floating window that shows the network of links from the current context. Like the menubar icon, it would dynamically update itself based on the selection or open resource in the foreground app. For apps that are most link-friendly using AppleScript, Hookmark the updating would be dynamic. For apps that use other means of automated linking (such as x-callback-url or UI scripting), you’d need to manually refresh the Graph View window, or select a bookmark in the Bookmarks window.
I like the sound of this. I can’t be sure how much I’d use it, but it’s clearly the case that I see things in visually presented information that I overlook in a list.
Visual representations are almost always better. I would use this. It’s a bit like the graph in Obsidian, but much more powerful in that it picks up items not inside the Obsidian silo.
Definitely interested in a graphical network view of hooked items, especially as part of a hook bookmark library management feature. Think of the way Personal Wiki systems (Obsidian, Org Mode, etc.) allow you to assess the network of interdependent links and update them to reflect your current understanding of the information and it’s use in subsequent projects.
Barring divine intervention of the UI gods it would probably be a distraction. I could find use of an inverted tree of links similar to the graphic assuming it was functional. Would I be able to add a link directly from pdf-a to pdf-c from within the graph or open a selected link? How many levels would it cover and would that be a selectable range? Etc, etc.
I’m not a bit interested. I’ve used Obsidian for years and love it, but I never use the graph view. I’ve looked at it a few times because it is pretty, but have never used it for anything productive. Don’t waste your time on bringing it to Hookmark.
Just adding my thoughts on what utility I am truly seeking from Hookmark. Between the “Hooked” and “Indirectly Hooked” lists that appear when I invoke Hookmark on a file (or other linkable object), I can quickly access items that conceptually “fan out” from the item I have selected, allowing for quick navigation to nearby items.
What benefit does the addition of network graph view UI give the user? It may come down to the user, who may be more visually oriented. In my usage, how close nearby doesn’t matter, I only need quick access to nearby items - which “Indirectly Hooked” caters beautifully for. A network graph view may show the same information, but the user would need to visually scan across it to pick out the item - I think a list is much cleaner and faster.
Underdeveloped thought here, but I use HM as an archive of connectedness. Invoking it thus enables me to rediscover sometimes unexpected connections that I have already established. That archive of connectedness also offers real convenience, moving back and forth across a group of hooked items.
The sort of larger scale discovery of connectedness that a graphic view nominally offers moves Hookmark toward being a different sort of tool - it shifts from being fantastic at making visible the interconnecting edges to instead focusing on the nodes.
I’m a happy user of the free version of the app, and the only reason I haven’t upgraded to the paid version is because navigating the hooks is super confusing. It’s hard to figure out how things are linked bidirectionally - and almost impossible if they are 2+ levels apart -, so I don’t see the point in paying for that feature. Does it have to be a node map? Maybe not, but if implemented well it could definitely work.
I’m delighted you’re getting mileage out of the free version, that’s what it’s there for.
We did a survey about adding a graphical network view, and most people who emailed us , CogSci Apps Corp., didn’t want us to spend our R&D on it. The cognitive load is actually higher with a network view. We have added an “indirectly hooked” section to Hookmark that helps you get to other items in the network and this feature is stunningly useful. We nonetheless might do the network eye candy at some point; but it’s not as much a priority as what’s currently in the product road map.
Just around the corner, this month, will release Hookmark Pal for iPhone and iPad; and Hookmark 6.9. E.g., we are fleshing out Hookmark’s menubar and making the foreground mode the default. Most users didn’t realize they could make Hookmark run in foreground. Advantages of foreground mode are:
Hookmark appears in the App Switcher
Hookmark appears in Force Quit list
Hookmark appears in the Dock
See
In an upcoming release of Hookmark, all apps and all app states will be compatible with Hookmark in that you’ll be able to create bookmarks associated globally with an app. Thus, No linkable item found in app will not be shown anymore!! Instead, you’ll have access to bookmarks that are global to the current app. So if you invoke Hookmark in the new Kindle app or Thunderbird, which both lack AppleScript, you’ll be able to create bookmarks that stand for particular books and messages, respectively. They will appear in a new section of the Context window (and of course in the Bookmarks window).
As for Hookmark 7.0… I wish we could talk about it because it’s going to be truly revolutionary (again!); but we can’t spill the beans about it just yet .
Thanks for your reply. Actually, after posting my message I decided to buy a license just because I felt unfair to not give back to the developers of such a wonderful tool. Although probably my experience will not improve much with the paid version.
Also, I would probably agree with those who think that investing time in developing a fancy graphical interface is not a good decision. In reality what I am lacking the most is a good visual cue which could easily tell me that the file I’m looking at is linked to something else (I know the menubar icon can do that but I don’t find it very effective).
The fact that hookmark works under the hood is a double edged sword: In my case, I usually forget that I have linked one document with other resources, so by instinct I navigate to those other documents manually instead of simply using hookmark. Which is the whole point of having this app!
.