I appreciate you effort very much. Glad to share some experience
I am long-time markdown (esp. MMD) user. I am using it for
everything: articles, blog posts, my personal wikis to pre-editing
large complicated documents/ebooks e.g. "4-Hour Body" by Tim
Ferriss (which we published in Czech language in iBookstore etc.).
The source has 1.2 MB of text…
I found there is a lot of "editors" or tools for md during the
last years, but only some of them are stable, consistent, open,
supported and "compatible" enough for bit more complicated docs
than for simple blogposts:
Multimarkdown Composer by Fletcher Penney (MMD-compliant,
behaves nearly flawlessly, realtime TOC, supports using direct HTML
tags in text)
Marked (as viewer and perfect combo for the Composer, with CSS
styling) by Brett Terpstra
I am using ByWord or nvAlt for shorter or simplier things
Other editors (Valetta, Mou, iaWriter etc. etc.) have problems
with interpretation of markdown (or do not intepret MMD, which I
consider the most valuable fork of md), are
not-able-to-open/are-completely-unstable when opening large
documents or whenever I want to add anything else than basic
formatting. There are even other problems: when rendering the
output (HTML/RTF), the results vary, because of markdown
interpretation when dealing with "special cases". The most problems
occur when intepreting spaces/tabs/code, in ordered/unordered
(+nested) lists (and between them), with pictures, links,
references and footnotes...
As for FoldingText: I like the idea, I would like to use it
instead of ByWord for shorter docs. But I noticed you are creating
your own version of md interpreter which (again) creates another
different output behaviour from the best existing tools yet. Is
this the right step? Would not it be better to offer something
which will be "sustainably compatible" (e.g. with "my combo") in
But I noticed you are creating your own version of md
interpreter which (again) creates another different output behavior
from the best existing tools yet. Is this the right step? Would not
it be better to offer something which will be "sustainably
compatible" (e.g. with "my combo") in long-term?
Are you talking about the realtime syntax highlighting, or the
“Export as HTML…” menu item?
If you are talking about the realtime highlighting… in
that case I think pretty much all apps need to implement this part
from scratch (and so are likely to differ in small ways).
It’s difficult, if not impossible to reuse the standard
Markdown.pl script to perform syntax highlighting in a performant
manner. If you run into specific cases where this is causing a
problem please let me know. (Though there are some markdown
syntaxes that I’ll likely never support since they convict
with other things that I’m trying to do).
If you are talking about FoldingText’s “Export as
HTML…” behavior, for that I’m using http://code.google.com/p/pagedown/.
But if you are looking for are more standard solution I would
recommend just using Marked… it’s designed explicitly
for the task and I think will always be better then FoldingText for
Anyway, if you have some specifics that I can address I’ll
certainly take a look.
I am not a power markdown user, but I do use it and have tried
quite a few markdown based text editors. I also use TP and WR on
both OSX and iOS.
I just tried FT and it looks great. My initial feedback is:
I'd like to see the folding option reinstated (I browsed this
forum and my understanding is that Jesse took it out just before
releasing the beta)
I want themes, of course
If I start seriously using FT on a regular basis, I'd like to
see (sooner rather than later) an iOS version (Dropbox-syncable, of
I'd like to see an RTF exporting option, although I agree that
Marked makes this request sort of irrelevant