This thread has shown up an unfortunate and unintended naming collision—looking at TBX v0.5.4.
In note “Publish single note to DEVONthink”, the code below declares a variable ‘linkPath’:
var linkPath(exportedString(l, "^path^"));
In 2018 that wasn’t problematic. But in v9.0.0, a new action operator linkPath(). I’m not sure how such a name collision is handled. But, even if the doc works, I’d suggest updating the TBX to use a variable with a non-clashing name. I avoid this by prefixing all my variable names with a ‘v’ which makes variable names immediately obvious. Of course, other naming methods are equally helpful - mine’s just one such.
I see that there was some discussion a while ago about getting this to work with Markdown (i.e. inserting a Markdown file into DEVONthink instead of an HTML file). Is this still possible with the latest version of Tinderbox? And/or is it possible to do the same with an RTF file?
Gunnar, thanks for updating the script (untested) to “markdown” from html. My preference too.
Quickly and as an addition,
I noticed in the quick and dirty attempt file, the old attribute $KeyAttributes is no longer used, it should be changed to the current name of $DisplayedAttributes in the 3 references noted below to
I’ve spent today exploring this topic and process: composing in TBX and processing / storing in DT has been something I’ve sought for some time but only recently got my comfort level up enough to give it a try. And it worked wonderfully! Thanks to all the contributors here.
@pat 's approach got me pointed in the right direction but needed the update from @gul-iMac to pull it off. Like @Julien my mindset and workflow relies on integrating images with text. I found I needed to modify his / her recommendation for image placement by (after dragging from DT) inserting a “!” as prefix to the DT ItemLink below the image in TBX - e.g.,
!x-devonthink-item://E85F32FD-211E-4EE8-AA1B-9A7AA502D5E9
Applying the Publish to DT Stamp to an image-containing TBX Note resulted in a nicely md-formatted file in DT.
In my trials, my most frequent cause for error has been forgetting to first apply the p_DEVONitem Prototype to the Note before applying the Stamp.