Bruce.

Alas, very hard. We know it sucks, it’s to do with the TinyMCE code and how it’s implemented. […] And code highlighting is a plugin for sure.

I appreciate the reply.

I discovered some plugins that may help. I’m yet to check them out, but if I find something good, I’ll share it here.

As for the DFW (Distraction Free Writing, aka Full Screen Editor), there’s a trade off to all the buttons and fewer. The idea is to cut down on distrations. 😉

What I was mostly saying is that the Visual “Distraction Free Writing” Full Screen Editor offers more buttons than the HTML Full screen editor.

You could say that people who would use the HTML editor won’t need those buttons, but since they make things easier and are already present in the visual DFW full screen editor, I don’t understand why they’re omitted from the HTML DFW mode. (Especially since switching between the visual and HTML editor isn’t really optimal at the moment.)

I love the experience of the distraction free writing mode, but find the nice experience of using it gets interrupted because, if I want to do basic functions that are, for me, essential to content creation (like easily apply formatting to text and preview what a post will look like, which is something I sort of have to do since switching to the visual editor messes with the HTML code), I have to exit the full screen mode.

I think giving users the option to have features like (1) somehow being able to preview a post from the full screen HTML editor and (2) having the same buttons available in both the HTML and Visual full screen editor would allow simplicity to be there by default, with functionality only an setting-change away.

My intent isn’t to be critical. I just like as many users as possible (me included, heh) to have a nicer user experience.