![]() ![]() On choosing a particular tag, this editor will provide you a code that is an example compatible with that particular tag. This is particularly important before you embed it into your specific code. With the help of these free CSS Editors the users can have a look at the changes almost instantaneously and can you have a firsthand impression about how the webpage will appear, and the effect it will have on your entire template. There are certain free CSS Editors which provide the user to incorporate new CSS and to distinguish the common CSS categories. It is the most widely used application to develop web pages that are written in HTML as well as XHTML. Links to forum discussions, tracker, docs, etc.16 Professional Free CSS and HTML EditorsĬSS or Cascading Style Sheets is a particular type of web language that is used in order to describe the different semantics (that is the get up as well as the presentation) of a particular document. Saving the changes will save the text (and format) as HTML.Īlthough we are losing some information, we feel it's an acceptable tradeoff against overall usability, particularly as the HTML editor works on a wider range of browsers and we make XHTML compliance a requirement. Proposal: whenever the HTML editor is used to edit existing non-HTML text, we convert the text to HTML for use in the editor. This really applies to all non-HTML formats. There is a bug ( MDL-4868) about Markdown not being converted to HTML when using the HTML editor (after creating a post with Markdown). FCKeditor needs to have its plugins in a specific place. ![]() TinyMCE makes it possible to have self-registering plugins, that don't need to be under it's /plugins folder (and so could be in a moodle-specific folder).It also may be possible to use Moodle's CSS files to define editors themes/skins, this needs investigation Multilang: all editors need to support multilang properly.Equation editor: there is ongoing work to get Dragmath working in Moodle, making a common plugin could be a nice improvement.We need a way to make for each editor to use Moodle strings, reusing as many existing strings as possible, and using lang/xx/editor.php for the rest. Language files: Moodle has a lot more languages than any editors, and some strings will be Moodle-specific.Emoticons (smileys): Moodle defines its own list of emoticons, we need to make sure the editors use these consistently.File browser: the file browser (especially with the File API) will be Moodle specific.Since editors will be located under /lib/editor, let's store this common code under /lib/editormod. These should be as abstracted as possible, to make as much code as possible common between each. Some plugins will have to be written for each editor to make integration with Moodle possible. Attack each Moodle plugin in turn, keeping modifications to TinyMCE code base as modular and minimal as possible.Have the XHTML profile active by default in TinyMCE (done).Get latest TinyMCE in HEAD before so that work can be done there (done, MDL-14739).FCKeditor: Compatibility Documentation, DemoĪs of 16 April 2008, the preference goes to TinyMCE.TinyMCE: Compatibility, Documentation, Demo.Comparison of WYSIWYG HTML editors on Wikipedia.Submit drafts in the background, using ajax.Fix all the bugs related to the HTML editor.Possible to run many instances on the same page (see MDL-11101 in tracker).Make it possible to change to a different editor (provided someone comes up with the necessary code to "plug it" in Moodle).Themeable (possible to make a theme that fits with Moodle's).Smileys (has to be possible to use the Moodle list of smileys).Possible to turn it on and off on demand (on the page) without losing (possibly modified) content (see this TinyMCE example of this).Highlighting (not text background color, with "set-on" operation-Word style).Support - Developed by an active community that will support it for a long time. ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |