Welcome, Guest. Please Login
Tinderbox
  News:
IMPORTANT MESSAGE! This forum has now been replaced by a new forum at http://forum.eastgate.com and no further posting or member registration is allowed. The forum is still accessible via read-only access for reference purposes. If you wish to discuss content here, please use the new forum. N.B. - posting in the new forum requires a fresh registration in the new forum (sorry - member data can't be ported).
  HomeHelpSearchLogin  
 
Pages: 1 2 
Send Topic Print
Exporting Notes Individually (Read 14255 times)
Ioa Petra-ka
Full Member
*
Offline



Posts: 103
Portland, Oregon, USA
Re: Exporting Notes Individually
Reply #15 - Jun 02nd, 2011, 4:41pm
 
Simplenote would provide the most seamless integration between the two applications. OPML is probably more powerful for one-shot transfers of bulk data (even if just to avoid a slew of heavy network traffic requests), but it's a one-way process. When you drag an OPML file into the Scrivener Binder, it creates an outline hierarchy based on the depth info, and populates documents using the text data embedded in the OMPL structure. Once this is done, that's it. If you want to update the material in Scrivener with a revised one from Tinderbox, you'll have to replace the old outline tree with the newly imported one.

Simplenote on the other hand will keep the content parallel between both applications. A helpful trick is to use Tb's document preferences to narrow down the sync list by tags (I think that needs 5.9.x+). Scrivener puts its own name into every note it syncs, as a tag, and it will also assign the project's code word as a tag, too. So you can not only tell Tb to only hunt for Scrivener assigned notes, but only those that pertain directly to your current work in progress.

Biggest drawback with this workflow is that Simplenote is a plain-text based system. So with the transport protocol being in plain-text, formatting will not sync. This isn't terribly awful in Scrivener as it is designed to work prior to final formatting anyway, but it will hamper some who do require it, and it will limit what all Scrivener/Tinderbox meta-text features (like linking) you can use. In Scrivener, definitely stick with inline footnotes and annotations, as these can be exported to Simplenote as bracketed text. ((Annotations)) and {{Footnotes}}. This way you can see and edit them anywhere, and even add new ones.

That's going to be a limitation with OPML, too. So I'd boil it down to this:

Do you need structure to be transferred? OPML will be your best bet.
Is all you need the content within the structure? Simplenote will do what you need; but it completely ignores structure (which note comes first, depth, etc).
Back to top
 
 

Av
  IP Logged
Derek Van Ittersum
Full Member
*
Offline



Posts: 168

Re: Exporting Notes Individually
Reply #16 - Jun 3rd, 2011, 1:52pm
 
Thanks for the explanation.  Looks like simplenote is the way to go for continual cross-talk between apps.  (brainstorming in TBX with maps, then syncing particular notes over to Scriv for integration into the document).
Back to top
 
 
  IP Logged
Pages: 1 2 
Send Topic Print