![]() Like Rob, I resorted to making a Markdown (preferably MultiMarkdown) file with BBEdit. This may be the purpose of a Hook Note file, but it’s not obvious how to add new links to an existing Note, or edit and re-arrange them. I never liked the way the Hook window disappeared as soon as one clicks away from it, and the new Hook window would show a different list. This could be a new floating Project window that can remain open and moved around, or it could be the existing Hook window made more persistent. IMHO, Hook needs a user-created Project window into which any link can be dropped, that can be re-arranged in any order by the user. This leads to what I find is the worst problem in concatenating research links: inconsistency. Hook links in a starting document may contain many links for that topic, but if a link is clicked to open another window in whatever application, not all the same links are listed in the Hook window. Rob has hit upon a drawback with the Hook system that has been bugging me since Beta-testing Hook 1.0 and which lead me to eventually abandon it. automatically saving it in in the TaskPaper file for the active project.Īll links in that file appear in a menu offered by a link-menu hotkey.link to copied address in another location,.copy as link (in one location) and then.I find that setting a default project for the current working session (as a KM variable, for example, or by setting a tag in a TaskPaper file), reduces the slightly cumbersome two-step business of the source of the KM-launched menu of Hook links when I am working on any file contained by that folder.the automatic-append destination of any new Hook links which I create with a KM keystroke,.using the taskpaper file in the project of that folder as:.Displaying instead the name of the project I’m working on and.It has hitherto been the text of the first line (in the working TaskPaper file of the day) that contains a tag, but I’m experimenting with: To put it all a different way, the key cognitive links are not, in fact, document -> document, they are really project ⇄ document.Ī ‘current context’ (displayed in the menu bar) is something which I have for some time used textbar to display in my macos menubar. Hook > Copy as Link well … to be honest … in this form … not so much ….Hook > Copy as Markdown Link is proving very useful.contains (inter alia) names of, and Hook-pasted Markdown links to, the current handful of active project folders.is always just one (Keyboard Maestro) shortcut away,.Contains all the Hook > Copy as Markdown Link URLs that the project accumulates and needs.Ī meta level of this, in my own case, is that I also have an ~/activeProjects.taskpaper file, which:.txt) summary file at the top level of that folder, which (inter alia) In the medium or long term for Hook, project-level link collections for the Hook GUI seem likely to imply a root and branch rethink of the DB structure, and possibly even of the central marketing metaphor, but in the meanwhile, I find that when I do use Hook it is in a simpler but still very useful mode, in which all projects: over time (different central documents at different stages of the same project.at a given moment (2 or 3 main documents in a given project), or.The current approach (link-collection menus available only from central working documents) inevitably fails us whenever a project has more than one central working document, either: The key weakness, at this stage, is in helping us find these URLs when we need them. The key function of Hook (at least in my workflows), is to quickly provide a URL for any document (and sometimes even, given the excellent scriptability, to sub-components of a document or database).
0 Comments
Leave a Reply. |