#2 Mar 16, 2016 03:08
The screen shots:
The screen shots:
These editors are very interesting indeed.
However the difficulty is that in our case we use many more renderers, not just markdown.
I am wondering if we need to develop JS previews for all our renderers.
Which view is the most useful for you:
Yes, it's really a heavy work if we preview for all renderers. In fact, the enhanced markdown and HTML preview pane are both useful for me, difficult to choose, even though the HTML preview could not show some rendered code correctly. (I agree that some users may get puzzled)
My idea was simple that just taking markdown render out and making it as a independent editor. Even without the HTML preview pane, i think it is also a step forward. Then there would be two possibilities:
For me, no matter which one to choose is all very good.
So at last , there are three editors: Markup(is it also necessary?), WYSIWYG and Markdown. This is not bad, isn't it ?
I think in this case we would actually replace the Markup "textarea" with a "syntax colored editor".
It is true we could start with coloring markdown and progressively add more. However, here again we would need to be careful as to what happens if people disable the "markdown renderer".
Another caveat: the markdown syntax recognized by the JS editor may be different from the markdown syntax recognized by the PHP renderer plugin.
Did you find more such editors in addition to the 2 you already posted?
@haharen Thank you.
We have researched a little about how to extend these editors in order to also take b2evolution's other renderer plugins into account. It seems pretty difficult. We will need to fork a script and will not be able to easily keep it in sync with further enhancements and bug fixes. We will research this some more.