Topic on VisualEditor/Feedback

Why not using an existant HTML5 editor?

10
81.50.158.182 (talkcontribs)

Raptor or Mercury Editor are really better HTML5 WYSIWYG editors than VisualEditor. Why not collaborate and adapt them to Mediawiki? Mercury Editor is not compatible with IE but is better than Raptor for the moment. But next version of Raptor is planning features that will render it as good as Mercury Editor. http://www.raptor-editor.com/demo http://jejacks0n.github.com/mercury/

Malyacko (talkcontribs)

How do these editors embed with wiki software? Are the parsers separate?

Jasper Deng (talkcontribs)

The Wikimedia Foundation decided that the existing wiki WYSIWYG editors did not meet its expectations. For existing HTML5 editors, they would have to be redesigned to handle wikitext, something that I believe was considered less feasible than writing a new one from scratch.

Jdforrester (WMF) (talkcontribs)

Yes - there's more on this in the "backgrounder" blog post about why we couldn't re-use an existing HTML editor, which otherwise would have made everything a lot easier on the VE front; however, we would still have needed to do the incredibly-hard work of building Parsoid, so it wouldn't have made things trivial.

27.252.173.255 (talkcontribs)

Raptor Editor have just released a major update including a ton of new features, improved documentation and improved plugin API - http://www.raptor-editor.com/

Trevor Parscal (WMF) (talkcontribs)

You are comparing apples and oranges here - Raptor and Mercury aren't really the same thing as VisualEditor. I appreciate the intention of your suggestion, but if you research the point further I'm confident you will find that VisualEditor is solving a different set of problems, most likely a super-set, but a different set nonetheless. We have requirements such as clean round tripping, whole document editing with protection of unsupported or generated content, and internationalization issues (just to name a few) that take a considerably different approach. We are always looking for ways to reuse existing open source code, and currently use jQuery, QUnit and Rangy. VisualEditor has been licensed under MIT to maximize reusability in and compatibility with other projects.

This post was posted by Trevor Parscal (WMF), but signed as Trevor Parscal.

78.247.32.88 (talkcontribs)

Yes, I'm comparing oranges and apples. Raptor is actually the easiest and ergonomic editor I know, VE isn't. Mediawiki should listen more to the needs of users or it could disappear one day.

Jasper Deng (talkcontribs)

It wasn't an easy decision to decide to develop its own. If you have suggestions for how to improve VisualEditor, see VisualEditor/Feedback.

PetahNZ (talkcontribs)

Just a note (from a core Raptor dev), if you want Raptor to do something/behave in a particular way I am happy to take feature requests/bug reports on our Github project.

Jasper Deng (talkcontribs)

If you come onto IRC, some developers of VisualEditor might be able to talk with you about it.

Reply to "Why not using an existant HTML5 editor?"