But themes for source window and for preview window is not designed and applied at the same time - they may not fit in when putting together. I appreciate that many markdown editor provide themes for users to choose. Non-Unified styles between source and preview This maybe a small issue, but still make me a little upset. Because different parser is used in source section and preview section, what I saw in source view may not be inconsistent when is is previewed. The second line is styled as in preview section, but styles as normal paragraph in source section. We can see “b” in source section is wrapped by while in preview section, it is not. Open for example, and input a_b_c in this source section. The worse thing is that: the markdown parser used for source highlight and preview is different. For example, use CodeMirror or Ace Editor to highlight code fences in markdown source while using Highlight.js for exactly same purpose in preview window or exported HTML, but since they are different code, the code fences may be parsed and highlight in different ways between source window and preview window. Behavior in source view and preview are not identicalĭevelopers sometimes use different technologies for source and preview. Therefore, I will concern the style and typesetting while I am supposed to fully focus on writing content. Also, when I concentrate on writing into the source view, since I don't know what it would look like after publishing, I may wonder whether the output is correct, due to the fact that different markdown editors has different dialect to parse/render markdown, I may take a look at the preview window to check outputs from time to time and unconsciously. For applications with a preview window, however, content inside the preview window keeps changing and rendering, which is very annoy to me. One benefits of markdown, as frequently quoted by many markdown editors, is that - the users does not need to care about the typesetting but only the content itself. When we chose a text editor just for writing, we want it to be Distractions Free. Therefore, I don't really want a preview view/window on my macbook. Many person wants it to support Markdown, but now it has 3 sections in this main window, thus if it supports markdown, it may end up with 4 sections in its main window since a preview section will be provided to user. Then think about a note-taking app like Evernote. It is even wrose when I want to use half of my litter screen to read documents and half of my screen to take notes via markdown - I will only have 1/4 area for writing with preview feature turned on. It might be acceptable if I was using iMac with a bigger screen, but on my macbook, I cannot accept that, only half of my screen displays useful information (for the other half just displays duplicated text content) text input is only allowed in a narrow textarea. Many editors, such as Mou, split their window into source section and preview section. There are more reasons for me to hate preview window: Separated views for source and preview means there are duplicate information on my screen. Markdown editor should help to achieve this goal, by using better syntax highlight design to reduce / eliminate noisy information (such as tags or formatting instructions) and therefore, make the content itself pretty to read, instead of providing a fancy preview window which indicates users to write in one place and read in another, since in latter pattern, the readability of markdown itself is underestimate. The principle of markdown’s syntax design is readable, in other words, it should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions. The overriding design goal for Markdown’s formatting syntax is to make it as readable as possible. So what’s wrong with most markdown editors ? Preview panel goes the wrong way Yes, there are many other markdown editors for mac, but I am not fully satisfied with any of them. Although it is in its early beta phase, I, personally, am very excited about my work and am using it as my default markdown editing & previewing app.
0 Comments
Leave a Reply. |