project: Moodle
summary: List of potential improvements to Atto HTML Editor
description: These are issues raised during peer review, integration and testing for the new text editor.

1.summary: Allow an editor plugin to be chosen per profile
description: At the moment we have a setting in the user profile: When editing text - use html editor /use plain text field. I propose that we change that field to allow selection of an individual html editor plugin on a per user basis. That way on moodle.org I can use damyons cool html5 plugin, and Martin can continue to use tinymce.
2.summary: Add Atto HTML editor to core (the editor formally known as contenteditable)
description: Add contenteditable text editor to core (non default). Link to plugins DB: Link to github: Also needs: to allow users to set their choice of editor in their preferences. Reasoning: 1. TinyMCE has bugs in iOS that we have been unable to solve in a reasonable amount of time. This editor is much simpler - so less to debug/maintain. We can leave tinymce as the default - but use this editor on iOS spcifically where tinyMCE fails. 2. It fits with Moodle better - it uses YUI for window management, and event handling - and uses moodle pix_icons etc - so the UI "fits" better with Moodle. Things to do: Change the name? - done - rename to "HTML5 text editor" Change the icons? - only for consistency. Can be done when icons are ready. If this is to be a core editor it needs to support enough of the features that TinyMCE supports so that it is not seen as worse. Some things tinyMCE does that contenteditable does not: Image alignment Maths plugins Colors Fonts Paste from word (Is this really needed?) More...
3.summary: Atto HTML Editor - Show the state of the text under the cursor in the buttons
description: Show the state of the text under the cursor in the buttons. IE when the cursor is in some bold text, change the appearance of the bold button.
4.summary: Atto - In html mode the other buttons are disabled but the visual difference is too subtle
description: HTML5 Text Editor : In html mode the other buttons are disabled but the visual difference is too subtle.
5.summary: Atto HTML Editor - Decide on the list of headings to include
description: HTML 5 Text Editor: Decide how many levels of headings to support and any other text styles.
6.summary: Atto HTML Editor - Provide more feedback when an action cant be performed
description: E.g. "And if I click the link button in the editor without having any text selected, nothing happens." It does not make sense to create a link with no text - so this should give some kind of feedback to indicate that this cant be done. Options: Error dialog Some kind of status bar at the bottom Flash the editable region and provide an access hidden message (my preference)
7.summary: Atto HTML Editor - Allow open in new window on links.
description: Add a checkbox for "open in new window" on the link dialogue.
8.summary: Atto HTML Editor - Move browse repositories buttons
description: Move them to the top of the dialogues (link, media and image) as they will be one of the most commonly used buttons.
9.summary: Atto HTML Editor - RTL support
description: Test RTL support and get feedback on whether we need a plugin for switching between LTR and RTL text.
10.summary: Atto HTML Editor - Table support
description: Is is needed? If so - what features?
11.summary: Atto: Move paragraph styles menu into to the other styles button group (bold/italic/etc)
description: Suggested by Fred and it sounds reasonable.
12.summary: Atto HTML Editor - Add a padding to the editable content area
description: As for now the written text is really close to the edge of the editable area, a little padding would be nice.
13.summary: Atto: Styles selector picks up styles from theme which makes it look crazy
description: Changing this to a plain list of links would look better.
14.summary: Atto: add ability to set margins when adding images
description: At present margins etc get hard coded. Fred suggested on that there should be an option to set them as well.

Below is an instruction that describes a task, paired with an input that provides an epic with this format: 
"project": "Name of the project" 
"summary": "Summary of the epic user story" 
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: List of potential improvements to Atto HTML Editor
description: These are issues raised during peer review, integration and testing for the new text editor.

### Response:
1.summary: Allow an editor plugin to be chosen per profile
description: At the moment we have a setting in the user profile: When editing text - use html editor /use plain text field. I propose that we change that field to allow selection of an individual html editor plugin on a per user basis. That way on moodle.org I can use damyons cool html5 plugin, and Martin can continue to use tinymce.
2.summary: Add Atto HTML editor to core (the editor formally known as contenteditable)
description: Add contenteditable text editor to core (non default). Link to plugins DB: Link to github: Also needs: to allow users to set their choice of editor in their preferences. Reasoning: 1. TinyMCE has bugs in iOS that we have been unable to solve in a reasonable amount of time. This editor is much simpler - so less to debug/maintain. We can leave tinymce as the default - but use this editor on iOS spcifically where tinyMCE fails. 2. It fits with Moodle better - it uses YUI for window management, and event handling - and uses moodle pix_icons etc - so the UI "fits" better with Moodle. Things to do: Change the name? - done - rename to "HTML5 text editor" Change the icons? - only for consistency. Can be done when icons are ready. If this is to be a core editor it needs to support enough of the features that TinyMCE supports so that it is not seen as worse. Some things tinyMCE does that contenteditable does not: Image alignment Maths plugins Colors Fonts Paste from word (Is this really needed?) More...
3.summary: Atto HTML Editor - Show the state of the text under the cursor in the buttons
description: Show the state of the text under the cursor in the buttons. IE when the cursor is in some bold text, change the appearance of the bold button.
4.summary: Atto - In html mode the other buttons are disabled but the visual difference is too subtle
description: HTML5 Text Editor : In html mode the other buttons are disabled but the visual difference is too subtle.
5.summary: Atto HTML Editor - Decide on the list of headings to include
description: HTML 5 Text Editor: Decide how many levels of headings to support and any other text styles.
6.summary: Atto HTML Editor - Provide more feedback when an action cant be performed
description: E.g. "And if I click the link button in the editor without having any text selected, nothing happens." It does not make sense to create a link with no text - so this should give some kind of feedback to indicate that this cant be done. Options: Error dialog Some kind of status bar at the bottom Flash the editable region and provide an access hidden message (my preference)
7.summary: Atto HTML Editor - Allow open in new window on links.
description: Add a checkbox for "open in new window" on the link dialogue.
8.summary: Atto HTML Editor - Move browse repositories buttons
description: Move them to the top of the dialogues (link, media and image) as they will be one of the most commonly used buttons.
9.summary: Atto HTML Editor - RTL support
description: Test RTL support and get feedback on whether we need a plugin for switching between LTR and RTL text.
10.summary: Atto HTML Editor - Table support
description: Is is needed? If so - what features?
11.summary: Atto: Move paragraph styles menu into to the other styles button group (bold/italic/etc)
description: Suggested by Fred and it sounds reasonable.
12.summary: Atto HTML Editor - Add a padding to the editable content area
description: As for now the written text is really close to the edge of the editable area, a little padding would be nice.
13.summary: Atto: Styles selector picks up styles from theme which makes it look crazy
description: Changing this to a plain list of links would look better.
14.summary: Atto: add ability to set margins when adding images
description: At present margins etc get hard coded. Fred suggested on that there should be an option to set them as well.
