Yes, it most certainly will/would. If you paste in the templates you need to make some modifications. Specifically add the user-generated attributes that my templates requires, $IsNoShowTitle, $IsNoShowText, $IsNoShowTitle, $HeadingOffset, $HeadingDepth, $Author, $Subtitle, $DateToday. You’ll need to adjust your Pandoc path as well. You may want to adjust the insertion of the author name, as Pandoc processes each not individual (can discuss this in detail at some later point).
Keep in mind. The Scholar template is an amazing example of the flexibility of TBX. The scholar template provides a tremendous number of customizable elements, all of which many people won’t need or ever use. So, don’t be afraid to dial back some of the customizations if you feel you’re getting overwhelmed.
Yes, it certainly would. It will depend on how you set up your attributes files, the use of templates, etc. Not to take away from the scholar template by saying this, but it is just that, a template. Templates and action code can be pasted into it, likewise the steps, methods, and ideas can be pulled out of it and put into other files.
You’re more than welcome, @andreas. This was fun to make. I conceived it for writing my thesis, but I switched to Scrivener for this purpose. My new master-template, that I use for new projects, is already very different. I will try to share it sometime in the near future, but there are many things to document for others to make sense of it.
There is no special reason for keeping the notes under a container that is a separator. I was working mainly on the outline (there was a bug that affected the note position in map-view if I moved it in outline view, so I stoped using map-view. This was fixed in the last beta version that should be publicly released sometime in the near future, I think).
To add footnotes, I used to use an applescript. See this file, and I think you’ll be able to make sense of it. You’ll need to run the script in script editor or with some other software (Keyboard Maestro, Alfred, etc.) due to a new bug with the runCommand action (probably caused by macOS).
Nice idea, I see how this stamp will automatically generate a foot note in the markdown format when applied. You still have to manually enter this note in your text I see.
I have another approach I’ll share on my Friday Patron session. The footnotes are automatically numbered based on their place in the document outline. That way you can move your text around and the footnotes will get renumbered. More on this later.
Thanks for this. I could not figure out why my osascript run commends had stopped working.
BRW, if you use the new “Shortcuts” app you can create an AppleScript shortcut and then use something like this in you action code, i.e. you tell it to run the name of your shortcut.
runCommand(shortcuts run "TBX and OmniFocus Create Project 1");
Hey Michael, this is the same file I sent you early last year (around May, I think). I couldn’t find my latest version of it. I remembered I had sent it to you per forum msg, so that’s where I got it from You are right, the approach is outdated, and there are many possible improvements, which I didn’t pursue because it felt like reinventing the wheel, and something I couldn’t afford to do.
My current take on this is that Tinderbox is amazingly flexible, but nowadays, I try to use it for things that would be more work in other apps instead of less. In most writing apps, creating working footnotes that will export adequately is trivial. And, despite the effort I put into Tinderbox Scholar, I can achieve the same thing more easily using Scrivener (with the aid of Pandoc or the built-in compile options).
That is not to say that trying to recreate these functionalities in Tinderbox isn’t great fun and a way to learn new things.
and yet: seing Tinderbox and Scrivener working more tightly connected seems just the next logical step. same is true for Tinderbox and Devonthink. @satikusala that would be a nice topic for one of the upcoming Tinderbox-Meetups. I would even try to contribute to that.
You are right, the approach is outdated, and there are many possible improvements, which I didn’t pursue because it felt like reinventing the wheel, and something I couldn’t afford to do.