21–30 of 36 posts
Very lame! This is much better, splitscreen, full screen, markdown, html code, or preview view. http://markdown.pioul.fr/
I feel like a lot of Markdown editors get posted on HN. Some of them seem pretty cool, but it gets hard to keep track of them all after a while. Has anyone tried keeping a running list of these editors with their pros and cons?
[¹] https://github.com/rhythmus/markdown-resources [²] https://github.com/rhythmus/markdown-resources/blob/master/m...
"Because, WYSIWYGs suck" I think this is a bit short sighted. I like Markdown and I'll eventually integrate it into my product, but to discredit the usefulness of WYSIWYG would be foolish. Maybe there is a lack of good implementations for it to show any value. I'm currently evaluating redactor ( http://imperavi.com/redactor/ ) as my WYSIWYG editor and I've been happy with it so far. For example this is how I render t…
wysiwyg is fundamentally flawed because the web is not wysiwyg. And HTML is a semantic description of content, not its formatting. We fought long and hard for that to be recognised, only for people to come along and try to derail that effort with wysiwyg editors. Case in point: the markup in your final link is terrible: tables for layout, inline styles, DIVs containing nothing by BRs, etc. I could never sanction the…
To be fair to Redactor, I was using an older version before its license change. It was something I quickly integrated a while back and it does introduce
and some other weird things. At the moment moment of writing the tutorial, I just needed it to "Look Right" and not technically be "Right" or "Pretty". My core product doesn't revolve around document management.
"I could never sanction the use of an editor that produces that kind of garbage."
The thing is, I'm willing to bet a lot of people couldn't care less about the HTML produced. In my case, I just needed to get the document out ASAP so that I could move on to the other hundred things on my to do list. I probably used redactor to put a square into a circle, but it got the job done for me.
"Don't get me wrong, Markdown is not the solution either"
I agree and who ever comes up with the solution, will probably do quite well. My reason for posting was to point out the Markdown isn't the final solution. For now, I'm willing to bet a lot of people just want to be able to type away and have things look right, with out it being right.
I feel like a lot of Markdown editors get posted on HN. Some of them seem pretty cool, but it gets hard to keep track of them all after a while. Has anyone tried keeping a running list of these editors with their pros and cons?
I maintain an inventory¹ of Markdown dialects, editors, parsers, stylesheets, etc. — basically just some lists with links. They’re in YAML, though, so you may want to add extra info (like a short description with pros/cons), and file a pull request. I am considering to split the list of editors² into one for native apps, and another for web-based implementations (such as EpicEditor). [¹] https://github.com/rhythmus/m…
-bowerbird
Earlier quoted context omitted.
wysiwyg is fundamentally flawed because the web is not wysiwyg. And HTML is a semantic description of content, not its formatting. We fought long and hard for that to be recognised, only for people to come along and try to derail that effort with wysiwyg editors. Case in point: the markup in your final link is terrible: tables for layout, inline styles, DIVs containing nothing by BRs, etc. I could never sanction the…
"Case in point: the markup in your final link is terrible" To be fair to Redactor, I was using an older version before its license change. It was something I quickly integrated a while back and it does introduce and some other weird things. At the moment moment of writing the tutorial, I just needed it to "Look Right" and not technically be "Right" or "Pretty". My core product doesn't revolve around document manageme…
People with disabilities, especially visual ones, rely on technologies that extract semantic meaning from your site's HTML in order to convert it to another form. If your HTML is garbage then your site is inaccessible.
"Because, WYSIWYGs suck" I think this is a bit short sighted. I like Markdown and I'll eventually integrate it into my product, but to discredit the usefulness of WYSIWYG would be foolish. Maybe there is a lack of good implementations for it to show any value. I'm currently evaluating redactor ( http://imperavi.com/redactor/ ) as my WYSIWYG editor and I've been happy with it so far. For example this is how I render t…
wysiwyg is fundamentally flawed because the web is not wysiwyg. And HTML is a semantic description of content, not its formatting. We fought long and hard for that to be recognised, only for people to come along and try to derail that effort with wysiwyg editors. Case in point: the markup in your final link is terrible: tables for layout, inline styles, DIVs containing nothing by BRs, etc. I could never sanction the…
Earlier quoted context omitted.
wysiwyg is fundamentally flawed because the web is not wysiwyg. And HTML is a semantic description of content, not its formatting. We fought long and hard for that to be recognised, only for people to come along and try to derail that effort with wysiwyg editors. Case in point: the markup in your final link is terrible: tables for layout, inline styles, DIVs containing nothing by BRs, etc. I could never sanction the…
The only sane solution I've yet seen is WYMeditor[1]. All the ease and immediacy of WYSIWYG, but producing proper standards-compliant code with the classes you choose. The code's not brilliant (having Rangy mixed in to cope with legacy IE annoys me), but the concept is so far ahead of anything else that I now use it pretty much exclusively for in-browser editing; as a professional writer I could never rewire my habit…
-bowerbird
I looked at this a while back, it's big and bloated. Despite having no real UI it requires jQuery UI... I don't understand.
Earlier quoted context omitted.
I maintain an inventory¹ of Markdown dialects, editors, parsers, stylesheets, etc. — basically just some lists with links. They’re in YAML, though, so you may want to add extra info (like a short description with pros/cons), and file a pull request. I am considering to split the list of editors² into one for native apps, and another for web-based implementations (such as EpicEditor). [¹] https://github.com/rhythmus/m…
by the way, thanks for maintaining that fantastic resource! -bowerbird
By the way: I’m very curious about your “zen markup language” in the make. Got some unfinished work in my drawers on “the best possible tool for writers”, too. Some more research, wireframes, and a few drafts on an _extensible_ markdown-like lightweight markup language. E.g. this little discussion: https://twitter.com/rhythmvs/status/423123272809455616
I sympathize with the idea of poet-turned-programmer. Maybe have a chat?