![]() As you know, many of us have been concerned about problems we’ve had contacting support, and getting feedback and answers to many, urgent technical problems. To be honest with you, there’s been quite a bit of chatter over concerns about your small staff and, by extension, the relative fragility of your product as it seems to be wholly dependent on one developer. ![]() Happy to explain further if you’d like – or you can just refer to my earlier posts about these concerns. – all of whom have been working hard to fix and clean up MN3-export files ! I say this not be hard on you guys, but in trying to help you understand how much work we’re doing to remediate the MN3-export files so that we can use them properly. In fact, I’ve been working with developers in OmniOutliner, iThoughtsX, Tinderbox, DEVONthink, TextSoap, etc., etc. Right now, almost all of the MN3-export files are clunky and problematic, and require quite a bit of clean up. I’d also add one important point: beyond including a CSV or Tab-delim exports and an UID in MarginNote-annotated files – and, by extension, the notes they create – MN users are desperately want the existing file exports to work. I think that sums up the answer to your format - features question. Once they’re solved, the folks at Tinderbox think they’ll be able to create better inter-app functionality with MarginNote.
0 Comments
Leave a Reply. |