TinyMCE is a platform independent web based Javascript HTML WYSIWYG editor control released as Open Source under LGPL by Moxiecode Systems AB. It has the ability to convert HTML TEXTAREA fields or other HTML elements to editor instances. TinyMCE is very easy to integrate into other CMS systems.
There are many forms of the editor that you can choose:
We often talk about one of the un-sexy core advantages of Ajax is the ability to do validation where you want it (right where the user is working) but validated securely on the server-side.
As we do this, we can offer interesting feedback to the user as they enter in the form data.
When you create an account at Google, they let you know how strong the password is as you type it. From too short, to weak, to fair, to strong.
You will see that they didn‘t whip together something on the quick, and spent time thinking about how to do WYSIWTG right.
Introduction
Rich text (WYSIWYG) editing on the web is a difficult problem. Browser-based rich text editors to date have failed to meet users stability expectations or in other ways subtly break the seamlessness of the editing experience.
JotSpot has been a key sponsor of Dojo and as the first Wiki to provide usable WYSIWYG, Jot‘s WYSIWYG editor is a critical part of the Wiki experience. While WYSIWYG is a clear advantage, it can be quickly undermined if niggling interaction problems or crashes make users distrustful or hesitant. Trust is earned slowly, but can be destroyed in the blink of an eye.
Testing showed almost every in-browser editor breaks user expectations or makes editing unstable. Of course it‘s not intentional. WYSIWYG on the web is a hard problem, and providing features cross-browser is a difficult feat. We‘ve all struggled against unhelpful APIs, lousy documentation, and a never-ending maze of bugs and feature requests. Amidst the frustration it‘s easy to forget that while it is possible to add a feature, endangering a solid experience is never worth it. What use is an editor if "undo" doesn‘t work? Do the semantics of an editor‘s output matter if it crashes?
A new editor that adhered to strict user-experience and reliability principles was needed. The results are the Dojo Rich Text, Toolbar, and Editor controls. JotSpot has generously made this work Open Source Software under the same liberal license as Dojo.
Core Principles of the editor
Do not break undo (Ctrl-Z works when possible)
Provide WYSIWYG, not source editing
Data Loss Is Unacceptable
Using the editor
The use of the editor follows the attribute markup philosphy.
To get the editor in your page, use the magic dojo class:
There are a lot of tree controls out there, but most of them are tacky, heavyweight relics of the "DHTML" era. I felt it was time for a change. In particular, I wanted to adopt "unobtrusive javascript" techniques. Among other things, the script has these notable features:
All of the styling is in a seperate CSS file. The only thing that the JavaScript manipulates is class names. This gives you a lot of control over the design relatively easily.
There is a no "set up code". The script searches for <ul class="tree"> and applies its magic to that.
All of the content as loaded in a set of nested <ul>s - the simplest, code that I could think of that was semantically linked to heirachical data.
Are we seeing an increase in unorbtrusive javascript controls?
