I get that the MN devs may not see (easy) use of data outside their app as a valuable feature. MN is a really interesting app - were it earlier in my studies I’d probably try and use it even if I’d still face the export issue if I wanted to use the notes in TB. The more I learn about inter-app data triage, the more I hold onto the fact that I’ve acquired niche skills not obvious to a wider audience obvious/simple is very much a subjective judgment. But, the user has a difficulty ( not through laziness) understanding /reading code and Applescript was a step I was trying to avoid (and has only become an option in v8). ![]() Indeed, I guess I could use Applescript in TB to locate the MN RTF url, place the actual URL in the TB attribute and then delete the otherwise unwanted $Text. Does that matter, why not just click the link in the imported TB $Text? Well, ‘No’, not if you wish to store the MN back-ref in a TB attribute. MN exports a back-ref to the item, by name of the PDF, with the MN pseudo-url as the embedded URL. To be open handed, a reason to ‘flatten’ RTF is that RTF-based links can’t (yet!) be accessed as TB links. Again, this isn’t to disparage DT, but in this it’s another purchase ‘just’ to get at MN notes and like Tinderbo, DT is a deep app that repays investment of time in understanding it, though that’s moot if it’s simply a pass-through medium. I know you’re a long-term and expert DT user. MN->DT->TB is OK, assuming you have and want DT. I’m not disparaging MN as an annotation tool, but simply pointing out some limitations from, IMO, poorly thought out export. I fear you quite misunderstand my point (though I’m sure not from ill-intent - so please don’t strike your comment above). It’s something to bear in mind when deciding to use otherwise well-lauded utilities - can you get your data out? Since Tinderbox v8 I’d probably use AppleScript to route around all the hassle, but MN doesn’t support external scripting.įrom 14+ years of community support for Tinderbox users the biggest pain is the hoops jumped though to overcome the inadequacies of apps used for initial note-taking/data-collection that totally overlook the fact that the information created likely needs using outside that app and yet having sub-par export methods. The plain text is then added to Tinderbox and processed using action code. ![]() The RTF is given some light cleaning in TextSoap to deal with some inadequacies in MN export before being saved as plain text. So, my take on OPML is try it: if it works, fine but if not don’t try to fix the edge cases and move on.Ĭurrently, the data is formatted - in terms of order and unique markers - in MN, then exported to RTF. One reason is OPML is quite a thin format mainly envisaged for passing an item’s date and title - most other things are ad-hoc enhancements to the format and thus prone to odd effects and unexpected edge cases. We tried the OPML route via iThoughts and had to give up. For all it does well, MN’s export is poorly thought out in terms of exporting a note’s structured data (text, tags, etc.) rather than as a single long-form text. textSOAP 3.2.1 is free for registered users, while the full version is available for US$19.95.I’ve been assisting a fellow user (in a private message thread) with trying to get data out of MarginNote (MN) notes and into Tinderbox attributes. You can find more information about the textSOAP update at the unmarked software Web site.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |