Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Editor 2.7: Difference between revisions

From MoodleDocs
No edit summary
No edit summary
Line 28: Line 28:
* Mobile support - how well does it scale on small screens?
* Mobile support - how well does it scale on small screens?
* Plugin support - can our community write plugins easily?
* Plugin support - can our community write plugins easily?
* Browser support - does it support all the browsers Moodle does?


== Candidates ==
== Candidates ==
Line 65: Line 66:
| Featureset
| Featureset
| 9/10
| 9/10
| 6/10
| 5/10
| 9/10
| 9/10


Line 83: Line 84:
| 10/10
| 10/10
| 9/10
| 9/10
|-
| Browser Support
| 10/10
| 10/10
| 10/10
|-
|-
| '''Total'''
| '''Total'''
| 34/80
| 44/90 (incomplete)
| 74/80
| 83/90
| 39/80
| 49/90 (incomplete)
|}
|}



Revision as of 06:25, 14 November 2013

Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please join the discussion on moodle.org or use the page comments.

Text Editor Revamp
Project state In Development
Tracker issue
Discussion https://moodle.org/mod/forum/discuss.php?d=243197
Assignee Jason Fowler @ Moodle HQ

Moodle 2.7


Project goals

The primary purpose is to update the default text editor in Moodle to a new editor.

This will improve accessibility, and usability, while replacing the now unsupported TinyMCE 3.5.8.

TinyMCE 3.5.8 will be kept in place for the next few releases, but will likely be disabled by default.

Along with the replacement of the Editor, plugins for TinyMCE 3.5.8 that are included as part of the Moodle release will be made compatible with the new Editor.

Considerations

  • Accessibility of the editor - is it at or easy to get it to WCAG AA?
  • Accessibility of the code produced by the editor - is it at or easy to get it to WCAG AA?
  • Maintainability of the links between the editor and Moodle - how much work will we need to do every time we upgrade?
  • Appearance of the editor - can it be modified to look like the other toolbars currently in Moodle?
  • Stong feature set - does it support the things our users have come to expect already?
  • String support - how difficult will it be to allow the strings to change when the Moodle language changes?
  • Mobile support - how well does it scale on small screens?
  • Plugin support - can our community write plugins easily?
  • Browser support - does it support all the browsers Moodle does?

Candidates

  • CKEditor
  • Atto
  • TinyMCE 4
  • ???
.. CKEditor Atto TinyMCE 4
Accessible Editor 8/10 9/10 ?/10
Accessible Content ?/10 9/10 8/10
Maintainable with Moodle ?/10 10/10 ?/10
Editor Appearance 8/10 10/10 8/10
Featureset 9/10 5/10 9/10
String Support ?/10 10/10 5/10
Mobile Support ?/10 10/10 ?/10
Plugin Support 9/10 10/10 9/10
Browser Support 10/10 10/10 10/10
Total 44/90 (incomplete) 83/90 49/90 (incomplete)


Sub Tasks

  1. Assess different editors
  2. Decide on an editor
  3. Implement editor
    1. Getting the new editor to render without altering the existing DOM - prevents changes needed to maintain third party plugins.
    2. Getting AMOS strings working within Editor.
    3. Getting Filepicker working within Editor Dialogs.


Mock-Ups

Related Tracker Issues