Board Thread:New Features/@comment-4079189-20150829183613/@comment-24473195-20150903104817

SpikeToronto wrote:

Dessamator wrote: Personally, I wish they'd merge the source editor with the code-editor, and simply disable some functionality e.g. themes,  wrapping, and highlighting by default.

All this jumping around through 5 different editors (VE, RichText, source ve, RichText source, code-editor) is a very bad UX.

I could not disagree more. Other than when editing CSS/JS, I very much prefer the nice old-fashioned, monospaced, black and white, source editor. And, that only works out to two different editing experiences.

I would truly hate to see my old-fashioned, monospaced, black and white, source editor disappear, unless personal CSS could be used to maintain the status quo for me. From a software development perspective two editing preferences is "one too many" (see  &  ). Especially when they mostly achieve the same thing. There is also a difference between personal taste and usability.

More importantly, that plain old source editor is worse than a MS-Dos based editor created 2 decades ago (e.g. "go to line" doesn't exist). There have also been studies conducted by the Wikimedia foundation [3] clearly indicating that editor isn't user-friendly.

The default design is also quite bad for real-time collaboration, which is functionality that the new Visual Editor project is eventually aiming to add.