I bookmarked this a week ago and am embarrassed to admit I had no idea it was that revolutionary.
>From my end-user POV I related it to the rendering of pretty-text from source markup (as in reST, markdown et al). It's a pretty tame example domain, but perhaps that makes it a realistic one for you programming gurus to tinker with, whether in Leo or separately to start with. Currently rich-text-via-markup editors have a range of interactivity models, I'll list a couple I've currently been working with in my toolchain quest: Old-school is of course edit plaintext in one window then "press a button" (run a script etc.) to check the result - "good enough" for most but can be a challenge to set up for end-users. One step up from this is within the same app, but still switching between edit-plaintext and view-rendered. Rednotebook is an interesting in-between, it's edit mode shows the markup in light-grey, semi-renders bold and headlines etc. Zim-wiki is a good example of WYSIWYG live rendering while editing, but requires jumping to an external editor to work directly in the plaintext markup. I'd really love to see one that offered the ability to choose either mode, or even show two panes side-by-side, letting you edit the plaintext in one with live rendering in the other **and** full editing in the WYSIWYG with live display of the changes to the plaintext in the other. And while I'm dreaming, have a plugin architecture to allow per-document choice of syntax - reST, LaTeX, the various extended markdowns (Pandoc first), maybe txt2tags, obviously raw html. Ah if I were rich I'd actually make this happen. . . -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/s107CNbHsuoJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
