Changes between Version 16 and Version 17 of Ticket #12875, comment 4
- Timestamp:
- Feb 11, 2015, 9:33:40 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #12875, comment 4
v16 v17 7 7 1. Both editors need short description how to use them. There should be a link that points to a documentation available @ http://docs.ckeditor.com/. 8 8 1. Use tooltips (simple HTML `title` attribute) to provide meaningful contextual help (remove separator, move group up etc.). 9 1. ** Olek:** Both editors' UX and UI must be polished.9 1. **DONE** **Olek:** Both editors' UX and UI must be polished. 10 10 1. Check whether the glyphs font used in the basic editor has the right license. We may also need to create a file in its directory with credits and its license. 11 11 1. The same as above about the CodeMirror and plugins used with it. … … 14 14 1. **DONE:** There's some error thrown right now. 15 15 1. **DONE:** We don't need the "Toggle editable" button. 16 1. ** Olek:** It would be good if toolbar buttons were not clickable. I checked that setting `pointer-events: none` on the toolbar element seems to be enough.16 1. **DONE** **Olek:** It would be good if toolbar buttons were not clickable. I checked that setting `pointer-events: none` on the toolbar element seems to be enough. 17 17 1. It's useful that the tool's width is proportional to window size - thanks to that one can check how the toolbar will behave in different widths. 18 18 1. The "others" group could be displayed in the table (https://github.com/cksource/incubator/issues/5). 19 19 1. **DONE:** In the basic toolbar editor change "Separator" to "Row separator" or something similarly meaningful. 20 1. ** Olek:** Reduce number of scrolls in the basic editor - there should be only one (I have two right now). (The floating toolbar makes sense.)20 1. **DONE** **Olek:** Reduce number of scrolls in the basic editor - there should be only one (I have two right now). (The floating toolbar makes sense.) 21 21 1. **Artur:** To be checked - how the toolbar editors read toolbar groups? What happens if one of loaded plugins defines its own group? What if it does and if `config.toolbarGroups` is set? This may be related - https://github.com/cksource/incubator/issues/4. 22 22 1. Toolbar editors should be checked on older IEs and if we have compatibility problems with something like IE10- we may just add there an alert that this browser is not supported. … … 28 28 1. Highlighting toolbar groups does not work on tablets or when one is using keyboard navigation only. 29 29 1. Check the style of "Unused elements" in Advanced configurator. 30 1. Bug: "Move up" button of a separator added without a context is enabled, though its the very first element of the list. 30 31 31 32 == Basic sample == 32 33 33 1. We can actually link to the `config.js` file in the section about setting configuration. This will be nice because someone may notice there that it got cached if forgot to clear cache.34 1. I think that unfortunately the width of the page must be static, because entire full toolbar should fit there. This means that the font size should be pretty big, so it looks ok in lower res.35 1. I guess that look of the basic sample should be inspired by the SDK.34 1. **DONE** We can actually link to the `config.js` file in the section about setting configuration. This will be nice because someone may notice there that it got cached if forgot to clear cache. 35 1. **DONE** I think that unfortunately the width of the page must be static, because entire full toolbar should fit there. This means that the font size should be pretty big, so it looks ok in lower res. 36 1. **DONE** I guess that look of the basic sample should be inspired by the SDK. 36 37 1. For the config section we chose `uiColor` and `height` which should cover 99.9% cases. We decided to place there entire code with `CKEDITOR.editorConfig = functio() {};`, so the text description must be updated accordingly. 37 38 1. Some users may look into basic sample's source code to see how the editor is initialised. This code is pretty complex due the compatibility checks. Therefore we can leave in comments some explanation why so and how to replace a simple textarea (important - code of the textarea should also be included). 38 39 1. Warning box below an editor should be displayed if the package doesn't include the `wysiwygarea` plugin. It should explain that without this plugin the classic mode will not work although inline editors and `divarea`-based ones will. 39 1. The text content of the sample that I created is already outdated. See Ania's document for the most recent version.40 1. **DONE** The text content of the sample that I created is already outdated. See Ania's document for the most recent version. 40 41 41 42 == Old samples ==
