Wikiwyg

From WhyNotWiki

Name:	Wikiwyg
	Upgrade Your <textarea>!
Homepage:	http://www.wikiwyg.net/
Documentation:	Wiki
Source code:	http://svn.wikiwyg.net/code/trunk/wikiwyg/ http://www.wikiwyg.net/download
Project/Development:	http://trac.wikiwyg.net/trac
Description:	Wikiwyg is a WYSIWYG browser editor framework for wikis. It is designed to be pluggable on top of existing wiki engines, with little or no change to the wiki engine's core software.
Implementation language:	Javascript mostly

http://www.socialtext.net/open/index.cgi?wikiwyg. Retrieved on 2007-05-11 11:18.

Wikiwyg is a WYSIWYG browser editor framework for wikis. It is designed to be pluggable on top of existing wiki engines, with little or no change to the wiki engine's core software.

Wikiwyg has been successfully integrated with the following wiki engines: Socialtext, Kwiki, MediaWiki, Trac and TWiki.

Wikiwyg is designed to be a modal editor. You can flip back and forth between WYSIWYG and WikiText and Preview modes in a single editing session. Other available/possible modes are Raw-HTML and Multi-User modes. Wikiwyg can even be configured to use just WikiText mode, and still provides many user benefits over a traditional textarea.

Wikiwyg currently support WYSIWYG mode in Firefox and IE 6+. It supports WikiText mode in those browsers, and Safari as well. In unsupported browsers, a Wikiwyg integration should fall back to the wiki engine's regular edit interface.

Wikiwyg Architecture (http://www.socialtext.net/open/index.cgi?wikiwyg_architecture#). Retrieved on 2007-05-11 11:18.

Wikiwyg is a JavaScript library that enables _in-browser WYSIWYG editing_ of Web content. It depends on features in Firefox (using Midas) and Internet Explorer (using DHTML commands) that let Web programmers make sections of a Web page editable. The browser features need some management, compatibility layers, toolbar and documentation support; there are a number of other WYSIWYG editing frameworks, like FCKeditor, Kupu, and TinyMCE, that do similar things. A lot of applications use these toolkits; others have custom code to manage WYSIWYG editing, like Yahoo! Mail and Gmail.

For many types of application that depend on a Web interface to generate user content (like wiki engines, blogging services, or Web discussion forums), WYSIWYG editing would be a great help for making a better user experience and consequently encourage user contributions. However, most of this kind of social software already has a markup system, like wiki markup, built into the server. So there's a disconnect between the WYSIWYG editing functionality in the browser, which has HTML as an output, and the Web software, which uses its own custom markup.

• Older or exotic browsers may not support in-browser editing
• Users or network administrators may have JavaScript turned off in the browser
• Experienced users may prefer the power of markup
• The server software is usually deeply dependent on the structure of the marked-up content

Some Web software simply abandons markup and stores and manipulates the returned HTML on the server side. For existing projects, this can require massive re-tooling of the server software; difficult manipulation of HTML on the server-side; and alienate users of older browsers or power users.

The Wikiwyg library supports Wiki markup and WYSIWYG editing; it makes it unnecessary for the server software to do any manipulation of HTML; and it degrades conveniently for older browsers or tight security settings.

Ross Mayfield (August 22, 2005). http://many.corante.com/archives/2005/08/22/wikiwyg.php. Retrieved on 2007-05-11 11:18.

This weekend we put something cool out into the world. Wikiwyg is what-you-see-is-what-you-get editor for wikis, or pretty much any other text area on the web. It's open source licensed, available for download and demo. Jeff Jarvis said wikiwyg is "the way wikis are supposed to be."

Our hope is this makes the two-way web usable. You can see the genius of Socialtext lead developer Brian Ingerson in something that is almost a bug, but might be a feature: double click anywhere to edit. Then you will notice it snaps into edit mode, as the editor was already loaded with the page -- reducing, but keeping, the distinction between display and edit mode. You can toggle between wysiwyg and wiki text (more efficient when you know it). Sexy Ajax pixie dust lets you edit without touching the server until you are ready to save. Always remember that Wiki Wiki is Very Quick in Hawaiian

[edit] Demos

How to use on Wikipedia: http://demo.wikiwyg.net/wikiwyg/demo/wikipedia/

http://demo.wikiwyg.net/wikiwyg/demo/standalone/ -- Shows how you can have it replace the rendered text with an edit box, when you double-click on some text (client-side -- without hitting the server).