Multimarkdown Composer and nvUltra

Luca Giancarli

December 23, 2019 10:19

Hi Fletcher and everybody, I love very much your hard work and I admit that Multimarkdown and Multimarkdown Composer have really changed my job and my life; that said, I have a simple question (hopefully not stupid): how do you suggest nvUltra and MMC work together? In other words, which are the differences between them? It seems to me that using nvUltra is not so farther as using MMC in pair with Finder. Thanks a lot 

0

• 

  Fletcher Penney

  December 23, 2019 18:52

  The core editing engine in nvUltra is the next generation of that used in Composer.  So the "editing experience" is very similar between the two (e.g. smart pairs, list completion, etc.) . Once nvUltra 1.0 has shipped, I'll be working on a major update to Composer that will use the new engine.  

   

  Composer is designed to help in writing "more complex" documents in MultiMarkdown and is built to take advantage of MMD in advanced ways, such as the drag and drop Table of Contents.  There are a few other features that are available, and a few more that are planned for the future.  Composer also has support for additional file formats (e.g. read/write support of OPML and iThoughts, as well as exporting to HTML, LaTeX, OpenOffice, etc.) . Composer also has a bit more GUI support for CriticMarkup editing than nvUltra.

   

  nvUltra's strength is in working with collections of documents -- e.g. a folder of random notes, documents related to a specific project, etc.  It is designed to allow you to work with non-text files in a more flexible way than Composer.

   

  When not programming, I am generally working with shorter documents/notes, TaskPaper to do lists, and mind maps (iThoughts).  I spend most of my time in nvUltra for this.  When working on a longer document (e.g. with chapters, sections, sub-sections) I switch over to Composer, but I might have been using nvUltra to navigate the folder instead of the Finder (as you mention).

   

  Some people will need both applications.  Some will only need Composer and some will only need nvUltra (and some will need neither application, but that's a different discussion...  ;)

   

  While the two apps serve different purposes, they will continue to share the same underlying core libraries to that there is a consistent experience, and that all bugs only have to be fixed once.

  1

Please sign in to leave a comment.