I’m currently not maintaining this application. Please use nvALT 2.2b instead for the time being.
Visit the up-to-date GitHub Source repository
Improvements I made
Note-taking is a popular topic amongst the so-called knowledge workers on the internet.1 Those addicted to plain text all praise the ability to sync their notes with their iOS-devices via SimpleNote. Interesting workflow descriptions based on this simple application are easily available online.2
Since early 2010 a new fork of Notational Velocity is available. In September 2010, I just hacked together a quick implementation of MultiMarkdown support for Notational Velocity. Since my digital archive (Zettelkasten) relies on MultiMarkdown syntax, my own need for such a tool huge. The current version sports support for the three most-popular markup languages I know.
- I heavily rely on Notational Velocity’s ability to find stuff quickly; the search field and notes list should be separated from the editor (for which I like to chose one myself as a user: TextMate, for example).
- Note creation does not work for me until the timestamp (note ID) and the basic header data is added automatically. These Zettelkasten-Features will be added.
- Browse, but do not view PDF and image files, which I sometimes add to my archive as well for references.
- It all began with Zachary Schneirov developing Notational Velocity and releasing it’s source code. Thanks to Zachary almost go without saying.
- Kudos go to John Gruber for making Markdown, Fletcher Penney for MultiMarkdown and Dean Allen and the people at Textpattern for Textile respectively.
- I thank the guys who implemented some sort of markup preview into Notational Velocity first (as far as I know): Steven Frank from Panic Software for his first Markdown-enabled fork and Guillaume-Jean Herbiet, author of the Textile-enabled version—without their work, I would not have started.
- Eddie Smith helped me put new ideas into the app, and without him being disappointed only having regular Markdown available, I wouldn’t have started tinkering with the code. His constant feedback (and exposure to the interwebs society of NV users) pushed me forward a lot.