Recommend this page to a friend! |
Classes of Jules Warner | WICMS | WIAdmin/WIInc/wysiwyg/README.md | Download |
|
Downloadbootstrap-wysiwygImportant information for Github requests/issuesPlease do not submit issues/comments to this repo. Instead, submit it to https://github.com/steveathon/bootstrap-wysiwyg Although this is the original repository, we need the project to be tiny and focused on the needs of the MindMup tool, which means that we do not want to complicate it with all the various bits and pieces needed for other usages and older browsers. Meanwhile, Steve was kind enough to create a fork, backport it to older browsers, extend and integrate all kinds of changes. Steve's fork does not need to stay small, slim and focused, so please use his repo for all your needs if this plugin does provide out of the box About the editorTiny bootstrap-compatible WISWYG rich text editor, based on browser execCommand, built originally for MindMup. Here are the key features:
Basic UsageSee http://mindmup.github.com/bootstrap-wysiwyg/ CustomisingYou can assign commands to hotkeys and toolbar links. For a toolbar link, just put the execCommand command name into a data-edit attribute. For more info on execCommand, see http://www.quirksmode.org/dom/execCommand.html and https://developer.mozilla.org/en/docs/Rich-Text_Editing_in_Mozilla
To pass arguments to a command, separate a command with a space.
You can also use input type='text' with a data-edit attribute. When the value is changed, the command from the data-edit attribute will be applied using the input value as the command argument
If the input type is file, when a file is selected the contents will be read in using the FileReader API and the data URL will be used as the argument
To change hotkeys, specify the map of hotkeys to commands in the hotKeys option. For example:
Styling for mobile devicesThis editor should work pretty well with mobile devices, but you'll need to consider the following things when styling it: - keyboards on mobile devices take a huge part of the screen - having to scroll the screen to touch the toolbar can cause the editing component to lose focus, and the mobile device keyboard might go away - mobile devices tend to move the screen viewport around to ensure that the focused element is shown, so it's best that the edit box is glued to the top For the content attachment editor on MindMup, we apply the following rules to mobile device styling: - edit box is glued to the top, so the focus doesn't jump around - toolbar is below the edit box - on portrait screens, edit box size is 50% of the screen - on landscape screens, edit box size is 30% of the screen - as the screen gets smaller, non-critical toolbar buttons get hidden into a "other" menu Dependencies
|