I’ll refresh this thread too. Since I come from a Web dev and programming background, I understand the challenges of integration. It’s tough. But luckily, with the web, integration has become a common tool, and API’s make integration far easier, despite the labyrinthine documentation often provided.
So why integrate Evernote with Scrivener? Because of two opposing forces: one, the desire of users for more and more functionality in Scrivener, and the opposite goal of keeping Scrivener lean and mean, devoid of the bloat that ruined Microsoft Word years ago.
Frankly, Scrivener is a tool best used on a desktop. There simply isn’t enough real estate on a phone or tablet to make best use of Scrivener’s organizational tools, which is probably why the programmers have struggled so much with the iPad version.
Evernote on the other hand, is DESIGNED for mobility and interactivity.
As a programmer, the best way to give Scrivener users what they want, while keeping the program lean and mean, is to interact with other existing packages like Evernote. Don’t reinvent the wheel, just use one from your neighbor.
Thanks to the Evernote API, two way integration is not only possible, but practically done by someone with the proper training. The Scrivener folks might want to hire a web designer who has Evernote API skills.
Here’s how I would envision a simple but powerful integration of both programs, each perfectly designed for their respective environments:
-
An Evernote notebook could be imported or linked to a folder in the Scrivener research section. Any notes in the Evernote notebook would be automatically imported at the next outline level down from the folder.
-
If linked, these Evernote Notebooks could be “synced on Scrivener open” or “synced manually.” Any new notes in the Evernote Notebook container would be added or updated as provided by the Evernote API.
-
If there is an Evernote format (like an audio for instance) that is unsupported in Scrivener, then scrivener would attempt to build a link, if the file is available on the web.
-
Once the Scrivener user copies the text from the research folder to the Draft section, all links and interactivity would be broken, and the text would stand on its own.
Evernote interaction would achieve the following for Scrivener Users:
a) Eliminate the need for Scrivener programmers to attempt a mobile version of Scrivener, allowing them to focus instead, on making the Desktop versions as perfect as possible.
b) Give us users a convenient way to assemble notes, research, and creative ideas on the fly, using our phones and tablets, by using Evernote, knowing that the information we assemble under specific notebooks would be readily available to us the next time we enter our Scrivener project.
Scrivener becomes much more powerful and web savvy, yet still lean and mean.