4 ms·
This looks really nice and elegant. It feels a lot like the built-in WordPad that comes with Windows, or TextEdit that comes with Macs, in that they both suppo
by crazygringo 6y ago
This looks really nice and elegant.
It feels a lot like the built-in WordPad that comes with Windows, or TextEdit that comes with Macs, in that they both support similar basic formatting but are also both historically built on RTF rather than HTML.
I'll admit I don't really understand the intended audience for this, however. Since it's not for webpages, it seems to be aiming at more basic text editing.
But hasn't Markdown pretty much become the de facto standard for that? For text documents, why would you ever want to write and edit in HTML directly, rather than easier-to-use Markdown that can be converted to HTML on the fly? (Especially with WYSIWYG Markdown editors existing.)
Just curious what I'm missing here.
- c-smile 6y agoThe intention was to have exactly Notepad but for structured HTML. Latest version: https://github.com/c-smile/sciter-sdk/tree/master/bin.win/x32 https://github.com/c-smile/sciter-sdk/tree/master/bin.win/x3... , two files from there: notepad.exe and sciter.dll It does support editing as in WYSIWIG as in Markdown form. Actually markdown is also form of WYSIWYG. But WYSIWYG on steroids I would say. Markdown format was explicitly designed to emulate WYSIWYG but in plaintext.
- ijidak 6y agoThis is great for content writers. For most article writing, the markdown workflow is inferior to using even a basic word processor. Often, when I write, I want to see the structure of the document visually. Markdown doesn't allow that. Also, I'm always writing for the web. I don't need the extra markdown to HTML step. What does that buy me? I think this aspect of HTML Wysiwyg is somewhat overlooked. Is this the next Hemingway app? Probably not. But for many of us, who write a lot of content intended for the web, this is a great tool to add to the toolbox.
- madsbuch 6y agoWhat you find futile I find the strength of the Markdown workflow: I really like the separation of writing and layout.
- c-smile 6y agoUnfortunately Markdown is too limited even for basic tasks. I wanted to write documentation in Markdown, it should be perfectly suitable for that, right? But this construct for example: <section> <header>method ABC</header> <p>Arguments</p> <dl><dt>...</dt><dd></dd> ...</dl> </section> has no Markdown representation at all.
- enriquto 6y agothis html is a bit "outdated", isn't it? in html5 you would ommit the unnecessary closing tags for p, dt and dd.
- madsbuch 6y agoI am not sure why this is a basic task? One could call documentation a very specific domain for writing and perhaps Markdown is not ideal for that? Personally I use it to write letters, notes, blog articles, and such. When I need to write something more complex I might or might not use markdown while embedding some other language. Eg. my thesis is written in Markdown but uses Latex. Depending on the context you can indeed use the concrete code you wrote as Markdown. You could insist on embedding the the <section> pieces into a Markdown document and use a markdown to HTML preprocessor. But you are the judge on whether this is a good idea.
- c-smile 6y agoYou just highlighted problems of Markdown. HTML supports wide range of applications. Even basic HTML provided more semantic value. You can use it as for articles as for structured documentation. As it supports hierarchical structure + classes. And pure markdown is not structural and not extendable by design - essentially just a flat list of paragraphs. Yes, you may have some containers there like <blockquote> and <ol> but that's pretty much it. Why there are no sections or any other form of grouping content? Markdown has exactly the same problem as MS Word / Richtext - they are very good in WYSIWYG but are terrible in semantic. Markdown.Next shall be in the golden middle between HTML and current MD - with modularity built-in by design.