<?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: Sucky Typo update</title>
	<atom:link href="http://hcoder.org/2008/08/19/sucky-typo-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://hcoder.org/2008/08/19/sucky-typo-update/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sun, 28 Feb 2010 17:11:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Harry Seldon</title>
		<link>http://hcoder.org/2008/08/19/sucky-typo-update/comment-page-1/#comment-186</link>
		<dc:creator>Harry Seldon</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-186</guid>
		<description>Handmade trackback :
I also got some problems with the text filters.
http://harryseldon.thinkosphere.com/2008/11/30/</description>
		<content:encoded><![CDATA[<p>Handmade trackback :<br />
I also got some problems with the text filters.<br />
<a href="http://harryseldon.thinkosphere.com/2008/11/30/" rel="nofollow">http://harryseldon.thinkosphere.com/2008/11/30/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fr&#233;d&#233;ric de Villamil</title>
		<link>http://hcoder.org/2008/08/19/sucky-typo-update/comment-page-1/#comment-187</link>
		<dc:creator>Fr&#233;d&#233;ric de Villamil</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-187</guid>
		<description>Hi,

I&#039;m the retard who dropped the live preview. There are a few reasons why I did that, and trust me, they are actually good reasons.

. What happened when you used the live preview? Everytime you type 2 or 3 keys, don&#039;t remember, an Ajax request was sent to the server, and Typo would generate a complete article, then display it. It did nothing but put serious servers on their knees, having Typo generating error 500 on many shared hosting. The final consequence was brocken, on even banned Typos on these platforms, and users could not determine why things were sucking that much (even happened to one of my ex co mainteners who dropped Typo for Wordpress because of it).
. Live preview was using Azure&#039;s stylesheet, which means it only rendered posts the way they would look when using Azure. Except to check whether or not your Textile / Markdown would render correctly, it was just useless.

I wish I had the time to write the live preview a better way, but at that time, I was supporting Typo on my own. My current co maintainer is working on a better system with a &quot;preview&quot; button,  much more sensible, and displaying your post with your theme&#039;s stylesheet. Release expected very soon, maybe before Xmas.

For your textile / markdown switch issue, I understand. I&#039;m also the retard who put that on a global way when I start an UI simplification. I will think about puting it back a more clever way (and on a per user basis).</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I&#8217;m the retard who dropped the live preview. There are a few reasons why I did that, and trust me, they are actually good reasons.</p>
<p>. What happened when you used the live preview? Everytime you type 2 or 3 keys, don&#8217;t remember, an Ajax request was sent to the server, and Typo would generate a complete article, then display it. It did nothing but put serious servers on their knees, having Typo generating error 500 on many shared hosting. The final consequence was brocken, on even banned Typos on these platforms, and users could not determine why things were sucking that much (even happened to one of my ex co mainteners who dropped Typo for Wordpress because of it).<br />
. Live preview was using Azure&#8217;s stylesheet, which means it only rendered posts the way they would look when using Azure. Except to check whether or not your Textile / Markdown would render correctly, it was just useless.</p>
<p>I wish I had the time to write the live preview a better way, but at that time, I was supporting Typo on my own. My current co maintainer is working on a better system with a &#8220;preview&#8221; button,  much more sensible, and displaying your post with your theme&#8217;s stylesheet. Release expected very soon, maybe before Xmas.</p>
<p>For your textile / markdown switch issue, I understand. I&#8217;m also the retard who put that on a global way when I start an UI simplification. I will think about puting it back a more clever way (and on a per user basis).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Esteban</title>
		<link>http://hcoder.org/2008/08/19/sucky-typo-update/comment-page-1/#comment-188</link>
		<dc:creator>Esteban</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-188</guid>
		<description>Hey Frédéric!

Ha ha, come on, I didn&#039;t call _anyone_ a retard.... and it was a rant after all ;-) Please don&#039;t take it personally, I was never my intention.

I understand the reasons to drop the old implementation of the live preview, but it was very disappointing not having it anymore after upgrading. And I personally hate web WYSIWYG editors, so that didn&#039;t help at all. About the themes and such, well, the only reason why I&#039;d ever use a preview is to check the syntax: sometimes I&#039;m not sure about the syntax of some less used options (like link aliases), or maybe I&#039;m not sure about how some strange combinations will render (links containing commas, a trailing comma after a link, a sentence in bold with an asterisk in the middle of it...).

I also wonder why the preview was completely dropped. I understand that the implementation for the live one sucked, but why not have a non-live one, to check before publishing the post? I love the preview feature for the comments, for example, and I find it awkward that for posts I have to send them live, then check if I wrote everything correctly, then edit afterwards blindly to try to fix things, all while people might be getting wrong versions in their RSS readers or browsers.

In any case, thanks a lot for stopping by and taking the time to reply and explain!</description>
		<content:encoded><![CDATA[<p>Hey Frédéric!</p>
<p>Ha ha, come on, I didn&#8217;t call _anyone_ a retard&#8230;. and it was a rant after all ;-) Please don&#8217;t take it personally, I was never my intention.</p>
<p>I understand the reasons to drop the old implementation of the live preview, but it was very disappointing not having it anymore after upgrading. And I personally hate web WYSIWYG editors, so that didn&#8217;t help at all. About the themes and such, well, the only reason why I&#8217;d ever use a preview is to check the syntax: sometimes I&#8217;m not sure about the syntax of some less used options (like link aliases), or maybe I&#8217;m not sure about how some strange combinations will render (links containing commas, a trailing comma after a link, a sentence in bold with an asterisk in the middle of it&#8230;).</p>
<p>I also wonder why the preview was completely dropped. I understand that the implementation for the live one sucked, but why not have a non-live one, to check before publishing the post? I love the preview feature for the comments, for example, and I find it awkward that for posts I have to send them live, then check if I wrote everything correctly, then edit afterwards blindly to try to fix things, all while people might be getting wrong versions in their RSS readers or browsers.</p>
<p>In any case, thanks a lot for stopping by and taking the time to reply and explain!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harry Seldon</title>
		<link>http://hcoder.org/2008/08/19/sucky-typo-update/comment-page-1/#comment-189</link>
		<dc:creator>Harry Seldon</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-189</guid>
		<description>&quot;then edit afterwards blindly to try to fix things, all while people might be getting wrong versions in their RSS readers or browsers.&quot;

Yup, to avoid that and to have a preview I publish first my posts in my Rails development environment of Typo. Not very practical.</description>
		<content:encoded><![CDATA[<p>&#8220;then edit afterwards blindly to try to fix things, all while people might be getting wrong versions in their RSS readers or browsers.&#8221;</p>
<p>Yup, to avoid that and to have a preview I publish first my posts in my Rails development environment of Typo. Not very practical.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
