Changes between Version 7 and Version 8 of Ticket #12875, comment 4


Ignore:
Timestamp:
Feb 9, 2015, 11:48:44 AM (10 years ago)
Author:
Wiktor Walc
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #12875, comment 4

    v7 v8  
    551. Config output format should be improved. As mentioned in https://github.com/cksource/incubator/issues/8 the format is ugly. Perfect solution would be as Ania mentioned - single quotes, nicely aligned and spaced. Acceptable result is that at least it will be nicely spaced and no double quotes. You can check the old toolbar tool because it was printing the config pretty well.
    661. The basic sample should link to the basic toolbar editor (the graphical one) which should link to the advanced one.
    7 1. Both editors need short description how to use them.
     71. Both editors need short description how to use them. There should be a link that points to a documentation available @ http://docs.ckeditor.com/.
     81. Use tooltips (simple HTML `title` attribute) to provide meaningful contextual help (remove separator, move group up etc.).
    891. **Olek:** Both editors' UX and UI must be polished.
    9101. 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.
     
    20211. **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.
    21221. 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.
     231. Introduce "headers" in Basic sample so that users were aware that there are groups and subgroups.
    2224
    2325== Basic sample ==
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy