Zettlr: feature: a wysiwyg review mode

Created on 2 Jul 2019  Â·  9Comments  Â·  Source: Zettlr/Zettlr

A preview mode already exist in Zettlr : right clic on a note in the tab bar activate a contextual window where you can clic on a preview item; but this preview activate a new window where you can see your text… in markdown, like in the editor mode (may be its only a problem on my french mojave (macOS 10.14.5) version ?).
Is it possible that the preview mode show us a wysiwyg preview ? More, could you assign a keyboard shortcut to this wysiwyg preview function ?

stale

Most helpful comment

@Miljanikus As i mentioned in your other issue, there's currently a WYSIWYG-module in the making, which I'll be activating once I've completed some more serious refactoring work! :)

All 9 comments

I left the preview plugins fully deactivated due to the fact that one should be able to copy the text out of the QuickLooks, which is easier if you see the full source code (remember Zettlr has a strict and strong focus on transparency, of you knowing what you actually write, not as Word does it, for instance). I mean I could offer a WYSIWYG-shortcut on the QuickLook windows, if that's what many of you want.

I don’t think that giving a wysiwyg QuickLook window is changing the philosophy of transparency of Zettlr. It’s not like a mixed view of markdown and wysiwyg as it could be in Typora or MarkText, that changes fundamentaly the philosophy of markdown and light markup languages.
But having a way to preview the result of the markdown code helps in the process of writing (as it helps to preview webpage on a code editor, and many editor implement their own preview mode), to verify if my code is good, or fully rendered by the app. For example, it could be better to see how a table/footnote/etc. is displayed while you’re writing it, as many markdown apps don’t render the table/footnote/etc. the same way. As my files are often created in a app, fully written in another and finalised sometimes in a third, it could be very useful to verify how they’re displayed.

Le 2 juil. 2019 à 09:22, Hendrik Erz notifications@github.com a écrit :

I left the preview plugins fully deactivated due to the fact that one should be able to copy the text out of the QuickLooks, which is easier if you see the full source code (remember Zettlr has a strict and strong focus on transparency, of you knowing what you actually write, not as Word does it, for instance). I mean I could offer a WYSIWYG-shortcut on the QuickLook windows, if that's what many of you want.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Zettlr/Zettlr/issues/258?email_source=notifications&email_token=AGFOZ274N7B6NZK5IZFVVHLP5L62FA5CNFSM4H4WLL22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZAKOWI#issuecomment-507553625, or mute the thread https://github.com/notifications/unsubscribe-auth/AGFOZ2YRPMOD4YDFBOEF34DP5L62FANCNFSM4H4WLL2Q.

I have a large number of notes and documents in markdown files, and I mainly use Zettlr both for writing and for organizing and reviewing records, and to a lesser extent for publishing in other formats. It seems to me very meaningful besides the source code of the editor's mod to have a preview of the formatted text without markdown syntax. The rendering of formatted text while writing, as in the Mark Text Editor, looks like a good extra option. Some of this is already offered option in settings (rendering of headings, citations ...).
In this way, everyone could choose the editor mode and adjust the program to their workflow.

@Miljanikus As i mentioned in your other issue, there's currently a WYSIWYG-module in the making, which I'll be activating once I've completed some more serious refactoring work! :)

Tnx!

Just wanted to add that it seems like many Markdown editors are based on the idea of "write it once, publish it elsewhere", whereby you write your text in an editor with a monospace font and all Markdown syntax visible without any (or very little) WYSIWYM/WYSIWYG features. This might work for blog posts but it's terrible for any workflows where you revisit what you wrote (regularly) in the editor. This occurs most commonly when taking notes and that is also the reason why I like Typora so much.

So, it's great that you are taking care of that. Do you have any ETA?

I seldomly do ETAs, because a plentitude of factors determine the development speed, among them my interest in certain features, the simplicity/complexity of them, and most of all, my time. So I can't tell you when it'll come.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This issue has been automatically closed due to inactivity. If you believe that this issue is relevant for many users and should not be closed, feel free to comment so that the admins will be notified.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rafedramzi picture rafedramzi  Â·  4Comments

volt4ire picture volt4ire  Â·  4Comments

Jos512 picture Jos512  Â·  5Comments

maehr picture maehr  Â·  3Comments

manisabri picture manisabri  Â·  4Comments