<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: WYSYIWYG Editors, The Back Button and a Monkey</title>
	<atom:link href="http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/</link>
	<description>Living in a state of accord.</description>
	<lastBuildDate>Wed, 10 Mar 2010 11:07:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ephox Blog</title>
		<link>http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/comment-page-1/#comment-52832</link>
		<dc:creator>Ephox Blog</dc:creator>
		<pubDate>Wed, 17 Jan 2007 19:54:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/#comment-52832</guid>
		<description>&lt;strong&gt;EditLive! 6.0 - creating web content just got easier...&lt;/strong&gt;

We are pleased to announce that EditLive! 6.0 is complete and can now be downloaded from our web site. This major release provides significant new upgrades: EditLive! Productivity Pack support Track Changes Thesaurus Equation Editor Content preservatio...</description>
		<content:encoded><![CDATA[<p><strong>EditLive! 6.0 &#8211; creating web content just got easier&#8230;</strong></p>
<p>We are pleased to announce that EditLive! 6.0 is complete and can now be downloaded from our web site. This major release provides significant new upgrades: EditLive! Productivity Pack support Track Changes Thesaurus Equation Editor Content preservatio&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Track changes is done! - Andy's blog</title>
		<link>http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/comment-page-1/#comment-39716</link>
		<dc:creator>Track changes is done! - Andy's blog</dc:creator>
		<pubDate>Thu, 16 Nov 2006 04:10:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/#comment-39716</guid>
		<description>[...] The best feature is content preservation. Apparently great minds really do think alike because AJ posted the same thing about three weeks ago. I found it funny that people in his comments tried to work out how we&#8217;ve done it, I wonder how many of those were actually developers on competing products. As much as I&#8217;d love to show off and point out the technical genius that was involved, we need to get paid somehow and this is a huge competitive advantage (even if it&#8217;s not a very marketable one) [...]</description>
		<content:encoded><![CDATA[<p>[...] The best feature is content preservation. Apparently great minds really do think alike because AJ posted the same thing about three weeks ago. I found it funny that people in his comments tried to work out how we&#8217;ve done it, I wonder how many of those were actually developers on competing products. As much as I&#8217;d love to show off and point out the technical genius that was involved, we need to get paid somehow and this is a huge competitive advantage (even if it&#8217;s not a very marketable one) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard O'Callaghan</title>
		<link>http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/comment-page-1/#comment-36456</link>
		<dc:creator>Richard O'Callaghan</dc:creator>
		<pubDate>Thu, 26 Oct 2006 18:19:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/#comment-36456</guid>
		<description>Adrian,

This is a very important feature which I totally agree will avoid numerous user problems with a WYSIWYG editor. This is one of the most obvious times when a user sends an angry email to support, because they&#039;ve lost maybe half an hours work.

And its present in some of the more prominent web applications around, including the blogging platform, Typepad.

Nice work! ;)

Richard</description>
		<content:encoded><![CDATA[<p>Adrian,</p>
<p>This is a very important feature which I totally agree will avoid numerous user problems with a WYSIWYG editor. This is one of the most obvious times when a user sends an angry email to support, because they&#8217;ve lost maybe half an hours work.</p>
<p>And its present in some of the more prominent web applications around, including the blogging platform, Typepad.</p>
<p>Nice work! ;)</p>
<p>Richard</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Sutton</title>
		<link>http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/comment-page-1/#comment-36387</link>
		<dc:creator>Adrian Sutton</dc:creator>
		<pubDate>Wed, 25 Oct 2006 20:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/#comment-36387</guid>
		<description>There&#039;s a major difference between using a user-agent to edit the page you&#039;re currently viewing and uploading it wholesale with a HTTP PUT than using an in-browser editor to edit a snippet of HTML from anywhere and submitting it back to a database. Now I know that HTTP PUT could use a database storage but it is fundamentally flawed in terms of editing experience. It has to edit the entire page, not just the content that&#039;s unique to the page and ignore any common navigation structure. It doesn&#039;t have a locking mechanism, change control, meta data etc. It&#039;s nice that the original web was planned to be editable, but it didn&#039;t happen and since then better techniques and technologies have been developed to edit web content.

If you&#039;ve worked with modern CMSs you&#039;ll see that they provide far more than was ever envisioned in the original concept of the editable web.</description>
		<content:encoded><![CDATA[<p>There&#8217;s a major difference between using a user-agent to edit the page you&#8217;re currently viewing and uploading it wholesale with a HTTP PUT than using an in-browser editor to edit a snippet of HTML from anywhere and submitting it back to a database. Now I know that HTTP PUT could use a database storage but it is fundamentally flawed in terms of editing experience. It has to edit the entire page, not just the content that&#8217;s unique to the page and ignore any common navigation structure. It doesn&#8217;t have a locking mechanism, change control, meta data etc. It&#8217;s nice that the original web was planned to be editable, but it didn&#8217;t happen and since then better techniques and technologies have been developed to edit web content.</p>
<p>If you&#8217;ve worked with modern CMSs you&#8217;ll see that they provide far more than was ever envisioned in the original concept of the editable web.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: karl</title>
		<link>http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/comment-page-1/#comment-36352</link>
		<dc:creator>karl</dc:creator>
		<pubDate>Wed, 25 Oct 2006 14:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/#comment-36352</guid>
		<description>What I mean is that… In-browser editors yes. It is the Web as it has been defined. The first browser WWW (re-baptized Nexus) was an editor and a browser. Every editing application should work in the Web (HTTP) metaphor. 

What I find silly is people designing javascript toolbars inside browsers to enhance forms. When a Web page can be modified directly with an HTTP PUT and edited in place.</description>
		<content:encoded><![CDATA[<p>What I mean is that… In-browser editors yes. It is the Web as it has been defined. The first browser WWW (re-baptized Nexus) was an editor and a browser. Every editing application should work in the Web (HTTP) metaphor. </p>
<p>What I find silly is people designing javascript toolbars inside browsers to enhance forms. When a Web page can be modified directly with an HTTP PUT and edited in place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Sutton</title>
		<link>http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/comment-page-1/#comment-36336</link>
		<dc:creator>Adrian Sutton</dc:creator>
		<pubDate>Wed, 25 Oct 2006 10:55:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/#comment-36336</guid>
		<description>karl,
What are you talking about? EditLive! is not AJAX and there are distinct benefits to having an in-browser editor instead of an external program such as when you happen to be editing content that&#039;s stored in a CMS etc.</description>
		<content:encoded><![CDATA[<p>karl,<br />
What are you talking about? EditLive! is not AJAX and there are distinct benefits to having an in-browser editor instead of an external program such as when you happen to be editing content that&#8217;s stored in a CMS etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: karl</title>
		<link>http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/comment-page-1/#comment-36335</link>
		<dc:creator>karl</dc:creator>
		<pubDate>Wed, 25 Oct 2006 10:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/#comment-36335</guid>
		<description>HTTP Put. Amaya. AOLPress. sigh. AJAX, an endless machine to reinvent the wheel.</description>
		<content:encoded><![CDATA[<p>HTTP Put. Amaya. AOLPress. sigh. AJAX, an endless machine to reinvent the wheel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Sutton</title>
		<link>http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/comment-page-1/#comment-36300</link>
		<dc:creator>Adrian Sutton</dc:creator>
		<pubDate>Wed, 25 Oct 2006 02:41:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/#comment-36300</guid>
		<description>Colder.... :)</description>
		<content:encoded><![CDATA[<p>Colder&#8230;. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Brondsema</title>
		<link>http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/comment-page-1/#comment-36299</link>
		<dc:creator>Dave Brondsema</dc:creator>
		<pubDate>Wed, 25 Oct 2006 02:38:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/#comment-36299</guid>
		<description>onBeforeUnload then (still untested).  E.g. http://www.4guysfromrolla.com/demos/OnBeforeUnloadDemo3.htm</description>
		<content:encoded><![CDATA[<p>onBeforeUnload then (still untested).  E.g. <a href="http://www.4guysfromrolla.com/demos/OnBeforeUnloadDemo3.htm" rel="nofollow">http://www.4guysfromrolla.com/demos/OnBeforeUnloadDemo3.htm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Sutton</title>
		<link>http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/comment-page-1/#comment-36297</link>
		<dc:creator>Adrian Sutton</dc:creator>
		<pubDate>Wed, 25 Oct 2006 02:26:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/10/24/wysyiwyg-editors-the-back-button-and-a-monkey/#comment-36297</guid>
		<description>Dave,
Go and test it and you&#039;ll find what the hard part is. :)</description>
		<content:encoded><![CDATA[<p>Dave,<br />
Go and test it and you&#8217;ll find what the hard part is. :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
