Hacker News new | past | comments | ask | show | jobs | submit login
Markdown Editor for web developers, on Mac OS X (mouapp.com)
190 points by chenluois on Oct 2, 2011 | hide | past | web | favorite | 79 comments



Those using MultiMarkdown[1], which this app seemingly doesn't support, may be interested in the MultiMarkdown Composer app[2] that should be out within a month or so. It's being worked on by the (very) active developer of MultiMarkdown and looks perfect for fans like myself.

[1]: http://fletcherpenney.net/multimarkdown/

[2]: http://multimarkdown.com/


That looks very nice, especially the TOC. I'd love to see it have a file-browser too similar to TextMate's, which is very nice if you like to organize MMD notes/docs in different files and folders.


MacOS only :(

Why don't people add that to the title? It would prevent non-mac users from getting their expectations up.


I launched last week an online Markdown editor that works in all recent browsers (IE support not perfect yet but will be).

It does intelligent preview (the paragraph being edited is kept into view and highlighted), has autosave and a simple document manager that lets you export HTML or markdown (RTF coming soon), and also has a converter, to convert rich text TO markdown (for your legacy content).

Check it out! It's called "Akayame" for Yet Another Markdown Editor, at http://akaya.me



@wladimir and @anatoly, thanks! I have updated the title - "Markdown Editor for web developers, on Mac OS X"


Use emacs.app with markdown-mode and docpad für (almost) live preview.

-jsl


Ah, right, thanks. Out of sheer lazyness of setting something up I generally use the built-in github editor and preview these days. It works pretty well.


Even worse, it ssays for Mac OS X Lion only (apparently according to the comments it should run in Snow Leopard). I'm quite sure an overwhelming majority of Mac OS users don't run Lion (in fact I know nobody running it ATM), and a significant part would rather wait for 10.8 because of all of 10.7 idiosyncrasies.


Doesn't say it on the page either until the very bottom.

It's almost as if it's a statement _not_ to say it upfront. It transmits the unspoken assumption that you don't care about anything else or you don't expect your visitors to.


That's ridiculous. There's a screenshot at the top of the page; it's clearly on Mac OS X, and it isn't as if it claims to be a universal app for the whole planet. Personally I think if the page began with a giant "ONLY ON MAC OS X" disclaimer that would look more like he only cared about that.

It was just an oversight in the Hacker News post title which has now been corrected.


No, it isn't ridiculous. I've seen many projects available for multiple OS's that choose to advertise themselves with a Mac screenshot (or a Windows screenshot, or a Linux screenshot) at the top. The screenshot by itself says it runs on Macs, but doesn't establish that it's Mac-only; you need to read all the way to the bottom to make sure of that. It's disdainful of a non-Mac user; that may be accidental, but I've seen this more often on Mac product sites than on Win/Linux product sites.

Your "giant ONLY ON MAC OS X disclaimer" is a strawman; what would be normal and courteous is simply mentioning that it's for OS X somewhere at the top. There are many, many product sites that do it successfully (e.g. http://www.hogbaysoftware.com/products/writeroom).

The post title on HN is a separate issue that's actually less of a problem. A random link to a product on HN doesn't carry an implicit assumption that it'll run on my OS. I don't mind clicking on it and discovering it doesn't (and besides, the author can't control the text of a link that leads to their site). But when I need to scroll down five pages on the site to ascertain I can't actually use it, that's irksome.



Could anyone explain to me the trend to write HTML in some other markup syntax? I write HTML in HTML. Going from one markup language to another seems like an extra unnecessary prereq.


Ideally, we would write everything in plaintext, but it doesn't support even the most basic features offered by typesetting (bold, italics, etc.) or hypertext (embedded links), so we turn to markup languages at the expense of readability.

Markup syntax like markdown, asciidoc, reStructuredText, etc. strive primarily to preserve readability with the least obtrusive syntax, and with a smaller learning curve (at least for the most basic usage).

So why use it instead of HTML? Like you, I typically write HTML in HTML, but often use asciidoc for other purposes (documentation, recipes, quick notes, etc.), because:

- One source document can output to multiple formats, like XHTML, LaTeX, PDF, DocBook, EPUB, Man page, etc. It's even trivial to output to a specific HTML DOCTYPE. That's pretty neat!

- Diffs are far more readable when not swimming in markup soup.

- HTML is overkill for many purposes. In fact, lightweight markup has its roots in email/newsgroup markup. HTML email is still a compatibility nightmare. Wouldn't it be great if a new standard for rich text email was developed, based on something as simple as markdown? It would be trivial to support it in webmail interfaces and the source would still be readable in plaintext email clients or if the sender went overboard with style choices.

- Archivability. Many old HTML documents render poorly in modern browsers, mainly due to style choices that seemed sensible at the time. Lightweight markup focuses more on the content and discourages going off on a stylistic tangent you may regret later. In other words, it does a good job of separating content from presentation, so your source documents will always remain readable and transform to something readable with relatively few tweaks in external stylesheets or configuration files.

Because it's easy to learn without getting lost in the arcane details of validation and compatibility, it's understandable why it's gaining popularity.


Obviously web design work should be done in HTML, or a very close approximation thereof (HAML). However, despite the link title above, Markdown isn't a web design language at all. It's for writing and editing copy, which is a very different task.

Let's say you have a bunch of untrained writers who needs to do some semantic formatting. They don't know HTML, so you can't ask them to just write HTML. If you let them run rampant with a WYSIWYG word processor (probably Word) you'll wind up with monstrosities where fonts were manually bolded and enlarged to indicate headers and such, and someone has to clean up after it.

If you have Markdown editors, though, you can turn an untrained writer loose with a cheat sheet ("write # to get a header" and such) and you're all set. As a bonus, you can put the Markdown document in version control, export to formats besides HTML, and a few other useful things.

Some major websites like reddit have also successfully made use of Markdown and its competitors to permit rich text comments from people who know nothing about HTML.


Using Markdown instead of HTML is much faster, and results in readable source text, whereas source HTML is hard to parse for the naked eye.


HTML is really verbose. I personally prefer HAML for my own stuff (it's like comparing the same doc in XML to YAML), but Markdown is definitely easy to read for programmers and non-programmers alike. Its intention is to read like a plain text email.

I would't say markdown is any easier to write because the verbosity of HTML tags and structure is usually taken care of with editor macros. It's definitely easier to read the source though.


Markdown is wonderful for simple documents often read in plain text.


I find it significantly quicker to write/edit the first draft in Markdown, then switch to HTML for final tweaks and formatting.

Do others keep their final versions in Markdown?


There's also Marked: http://markedapp.com/

I have no affiliation, just a happy customer. MacVim + Marked side by side is a neat combo.


Marked is a Previewer, not Editor. :)


A new Markdown editor for Mac I made, it's still in early beta stage. Requires OS X 10.7+ to run.

:)


Why does a text editor and a renderer with a fraction of the complexity of a browser engine require 10.7?


It can runs on OS X 10.6 but not officially supported. Features like Layout Orientation, Find bar, Full screen, auto save are using OS X 10.7's API.


Awesome, and very handy! One important feature request for developers: Support Github-style code blocks, e.g.

```

some code

```


Thanks for your suggestion!


Every time you make a change it scrolls the preview window back up to the top, making the live preview kind of useless.


I definitely agree. I'd like to see it automatically scroll the PREVIEW relative to where the cursor is in the EDIT view. Maybe this would get annoying but it's worth a shot.


I'm thinking a way to improve the scroll behavior. :)


Awesome... if there was a mode where it could auto scroll to where the cursor was then that would be heavenly.


Hi all!

There're just too many comments and I can't watch this page minutes by minutes.

If you have questions or suggestions, please email me directly.

Thank you very much!

:)


Looks great. Just a suggestion, I'd add another download link to the top of the page.


Very fine. I would suggest that you let the right pane follow the scroll position of the left pane (Or really - just have one scrollbar for them both). I know this isn't easy to accomplish, but it would really make a difference.


Thanks for your suggestion! I'll see if I can find a good method to implement it.


Looks pretty sweet. Markdown really is coming into a golden age, its everywhere: git readmes, stackoverflow posts, i'm even using it to write my presentations in these days! Love it :)


I'm just wondering why Creole wiki syntax failed on this particular point: for me, the syntax is much more consistent and easier to parse.


Markdown took email/mailing list/usenet conventions and turned them into syntax.


The HN crowd isn't everyone. Markdown is just another markup among hundreds.


It's great !

I just have two small requests. First, it seems you're using libdiscount (or objc bindings to libdiscount) to compile markdown, could you give the ability to pass flags to the compiler ? (e.g. activate footnotes). Second but less critical to me, I'd love to be able to tweak the CSS of the generated page (less critical because I can just tweak the style.css file in ORCDiscount).

If Mou had those two (small) features I'd gladly donate/buy it when it comes out.


Thanks for your suggestion! Replied you in Email. :)


Reminds me a lot of iA Writer (which is a commercial markdown editor): http://www.iawriter.com/


StackOverflow published their greatly extended bugfix of the original markdown web editor as OpenSource. They named it pagedown IIRC.


Eclipse.org Aptana has a plugin for editing markdown, but i don't remember coming across a live preview feature. Usually use Dingus for preview http://daringfireball.net/projects/markdown/dingus so i'm gonna give this app a go in about 15m


Thanks for this, I've been looking for a nice simple markdown editor that can kick out HTML for a while. I used to use TextMate's with it's Markdown preview, but since I stopped using TextMate I've needed something to fill that space. (Sublime Text 2 doesn't seem to have a preview feature)


You know, I'm glad you like Mou. :)


I'm on snow leopard, so this might not be a bug as you said it runs on SL unofficially, but it's VEERY annoying that every time I edit the 'source' on the left, preview jumps up to the beginning and I have to scroll all the way down to where I was. This is unbearable for long articles.


Having this issue on Lion as well. The 'flashing' in the preview pane in general is pretty noisy on the eyes.


Don't worry, I'm thinking a way to improve the scroll behavior. :)


Looks great. Any chance you can make the line-height adjustable? I find the editor a little too squished.

It would also be useful if users could supply their own css for the preview rendering...that way you could see what it'll look like with your own stylesheet.


The scrolling needs some work as well. It seems as soon as I write anything, the preview just shoots back to the top. Ideally it would follow me as I type and the two would link up transparently and smoothly.


@latch, thanks for your suggestion, "custom line-height" and "Improve scroll behavior".

Custom css for preview rendering is already possible now. Simply edit the css file inside Mou's app bundle:

http://cl.ly/AaUT

But do backups first!

:)


Just a note, it'd be awesome if there was some way to specify the stylesheet used in the preview pane, I'd love to be able to see exactly how the result will look on my site.


It's already possible. Simply edit the css file inside Mou's app bundle:

http://cl.ly/AaUT

But do backups first!

:)


This is already awesome, great work. However, if you integrated this with Simplenote, or a similar service, it would be even better.


Thanks for your suggestion!


Very nice, love the color scheme and content preview. Will it be free once off beta?


Color scheme looks to be basd on Solarized:

http://ethanschoonover.com/solarized


Not decided yet. But if 1.0 turned into shareware, all the people who donated during beta will receive a license for free.


That's what I was wondering, donating or buying it eventually, will be good to write a note on donation, so people like me know what will be happening :)


Thanks! I just added a note below the download button. - "Note: All the people who donated during beta will receive a license for free when Mou 1.0 released."


Hashify.me may not have as many features but it is a web-based version.


Yeah Hashify.me is made by my friend David Chambers.


Darnit! I had this EXACT same idea. Even the layout was the same in my mind. I'm not mad at the developer, major props for the hard work. But I AM mad at myself and hopefully this will serve as a reminder to future me that I should execute on my ideas.


Possibility to write using vertical layout is a pleasant surprise.


Yeah, Chinese and Japanese people will enjoy vertical layout. And perhaps Korean will like it too. :)


Don't forget about people learning these languages—they sometimes are even more concerned about vertical writing than natives, AFAICT =)

(OT: Nice clean personal website you have there.)


That may be true. :)


This looks amazing, but is it available for snow leopard?


It can run on snow leopard, but not officially supported, some features will be lost.

If possible, run it on Lion. :)


The download link states it's 10.7 only


Is there anything similar for LATEX?


Check out WhizzyTex mode for Emacs, which also lets you have an auto-updating preview beside your code for LaTeX.


Please someone do this with HTML.


A while ago I wanted something similar and could not find it, so I decided to put this together http://jrmoran.com/playground/markdown-live-editor/. It has some minor bugs and I have not updated it in a while.


Strictly speaking, Adobe has: it's called Dreamweaver.


While it's probably not exactly what you're looking for, Safari's Snippet Editor is great for whipping up some quick HTML with auto preview. Accessible via the menu, Develop > Show Snippet Editor.

No syntax highlighting which is kind of a bummer.

http://i.imgur.com/omtFb.png


Wow I'd never seen that before, very useful little tool.


I think KDevelop has something like that.




Registration is open for Startup School 2019. Classes start July 22nd.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: