Markdown Editor
joncom.be
joncom.be
This is from Sept 2010, so it seems a bit outdated.
For my site, I've been using the code [1] which powers the StackOverflow editor and it works great. It would be pretty easy to set that code up in a page like this one above and you'd get buttons for making things bold, which seems handy.
I guess there is similar tools for Linux and Mac OS X.
http://sourceforge.net/p/retext/home/ReText/ (Python and QT)
> The missing Markdown editor for web developers
given that there are many, many markdown editors on OSX. But after seeing the vertical Chinese layout, I'm really impressed! That's cool.
In answer to your question, attacklab did the hard work and yes there is an open source license attached to his/her work.
List items are added automatically and you can use shortcuts for the most frequently used markdown tags such as bold, italic, code listing, images etc. It also uses it's own undo/redo manager for more granular control.
markItUp! allows you to build wysiwym (What you see is what you mean) text editor and apply it to all HTML textareas
Pylowiki https://bitbucket.org/russellballestrini/pylowiki/src
markItUp! http://markitup.jaysalvat.com/
Pylowiki Demo http://www.foxhop.net
My interface isn't nearly as friendly or clean. But tab indention works, so I got that going for me at least.
Just wanted to leave this here.
This rule is quirky -- sometimes you'll end up with (for example) bullet points merged into a paragraph through this quirk.
As I understand it, Markdown syntax was inspired by email syntax, so we have > for block quotations, * for unordered list items, etc. By this reasoning, a single newline may just be the email client wrapping the text, whereas a double newline means the writer is starting a new paragraph.
Initially I wrote it against the Daring Fireball spec but switched it over to track the output of the showdown javascript library.
Markdown is not a great language to implement. I wrote a hand parser because there are loads of places where you have to look ahead more than one token (not that I am a great lexer/parser expert).
Outside that, nicely done :)