<?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: Elastic Tabs</title>
	<atom:link href="http://www.red-sweater.com/blog/154/elastic-tabs/feed" rel="self" type="application/rss+xml" />
	<link>http://www.red-sweater.com/blog/154/elastic-tabs</link>
	<description>Mac &#38; Technology Writings by Daniel Jalkut</description>
	<lastBuildDate>Mon, 15 Mar 2010 15:05:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: geoff.mollyandgeoff.com &#187; Monday Links</title>
		<link>http://www.red-sweater.com/blog/154/elastic-tabs/comment-page-1#comment-9319</link>
		<dc:creator>geoff.mollyandgeoff.com &#187; Monday Links</dc:creator>
		<pubDate>Sat, 15 Jul 2006 04:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/154/elastic-tabs#comment-9319</guid>
		<description>[...] This debate will never be settled.     &#160; [...]</description>
		<content:encoded><![CDATA[<p>[...] This debate will never be settled.     &nbsp; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Jalkut</title>
		<link>http://www.red-sweater.com/blog/154/elastic-tabs/comment-page-1#comment-8575</link>
		<dc:creator>Daniel Jalkut</dc:creator>
		<pubDate>Tue, 04 Jul 2006 14:05:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/154/elastic-tabs#comment-8575</guid>
		<description>Sorry about that Michel. WordPress (or my configuration of it?) has some funky postprocessing that sometimes bites things like this. I face the problem sometimes in posts, too, where I need to carefuly replace &lt; with &lt; to get the desired effect.  If you can either get another comment posted here or email me the unadulderated content, I will make sure it looks good in the original comment and then delete these fixup comments :)</description>
		<content:encoded><![CDATA[<p>Sorry about that Michel. WordPress (or my configuration of it?) has some funky postprocessing that sometimes bites things like this. I face the problem sometimes in posts, too, where I need to carefuly replace < with &lt; to get the desired effect.  If you can either get another comment posted here or email me the unadulderated content, I will make sure it looks good in the original comment and then delete these fixup comments :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michel Fortin</title>
		<link>http://www.red-sweater.com/blog/154/elastic-tabs/comment-page-1#comment-8569</link>
		<dc:creator>Michel Fortin</dc:creator>
		<pubDate>Tue, 04 Jul 2006 12:12:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/154/elastic-tabs#comment-8569</guid>
		<description>Oops! Apparently I shouldn&#039;t have posted a regular expression with &lt;code&gt;&lt;?&lt;/code&gt; in it: most of it got swallowed as a tag. And the &lt;code&gt;&lt;pre&gt;&lt;/code&gt; tag didn&#039;t pass either, so spacing isn&#039;t right even in the second example. I hate JavaScript live previews which can&#039;t show you what really happens when you submit.</description>
		<content:encoded><![CDATA[<p>Oops! Apparently I shouldn&#8217;t have posted a regular expression with <code>&lt;?</code> in it: most of it got swallowed as a tag. And the <code>&lt;pre&gt;</code> tag didn&#8217;t pass either, so spacing isn&#8217;t right even in the second example. I hate JavaScript live previews which can&#8217;t show you what really happens when you submit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michel Fortin</title>
		<link>http://www.red-sweater.com/blog/154/elastic-tabs/comment-page-1#comment-8566</link>
		<dc:creator>Michel Fortin</dc:creator>
		<pubDate>Tue, 04 Jul 2006 12:04:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/154/elastic-tabs#comment-8566</guid>
		<description>These elastic tabs are nice, but they\&#039;re going to clash with indentation in some cases. (The first code sample rely on proper indentation which did not work with the live preview, let\&#039;s hope it will work once submitted.) Here is a big regular expressions comming from PHP Markdown for which this particular kind of indentation won\&#039;t work (unless you insert a lot of blank lines):

&lt;pre&gt;&lt;code&gt;$text = preg_replace(\&#039;{
        (                         # $1: Marker
            (?&lt; !\\*\\*) \\*\\* &#124;   #     (not preceded by two chars of
            (?&lt;!__)   __       #      the same marker)
        )						
        (?=\\S)                    # Not followed by whitespace
        (?!\\1)                    #   or two others marker chars.
        (                         # $2: Content
            (?:
                [^*_]+?           # Anthing not em markers.
            &#124;
                                  # Balence any regular emphasis inside.
            ([*_]) (?=\\S) .+? (?&lt;=\\S) \\3    # $3: em char (* or _)
            &#124;
                (?! \\1 ) .        # Allow unbalenced * and _.
            )+?
        )
        (?&lt;=\\S) \\1             # End mark not preceded by whitespace.
    }sx\&#039;,
    \&#039;&lt;strong&gt;\\2\&#039;, $text);&lt;/code&gt;&lt;/pre&gt;

And even with inserted blank lines it\&#039;s never going to solve something like this either:

&lt;pre&gt;&lt;code&gt;$conversion_table = array(
    \&#039;a\&#039; =&gt; array(\&#039;à\&#039;,\&#039;â\&#039;,\&#039;á\&#039;,\&#039;ä\&#039;,\&#039;ã\&#039;),
    \&#039;e\&#039; =&gt; array(\&#039;è\&#039;,\&#039;ê\&#039;,\&#039;é\&#039;,\&#039;ë\&#039;    ),
    \&#039;i\&#039; =&gt; array(\&#039;ì\&#039;,\&#039;î\&#039;,\&#039;í\&#039;,\&#039;ï\&#039;    ),
    \&#039;n\&#039; =&gt; array(                \&#039;ñ\&#039;),
    \&#039;o\&#039; =&gt; array(\&#039;ò\&#039;,\&#039;ô\&#039;,\&#039;ó\&#039;,\&#039;ö\&#039;,\&#039;õ\&#039;),
    \&#039;u\&#039; =&gt; array(\&#039;ù\&#039;,\&#039;û\&#039;,\&#039;ú\&#039;,\&#039;ü\&#039;    ),
    \&#039;y\&#039; =&gt; array(            \&#039;ÿ\&#039;    ),
    );&lt;/code&gt;&lt;/pre&gt;

But for both code samples, I suppose a different layout could be used, maybe it would be less pretty but it would still work, while the rest of the code benefits from elastic tabs. But while it wouldn\&#039;t work everywhere, I have to admit I like the idea of elastic tabs. It could be a real time-saver.</description>
		<content:encoded><![CDATA[<p>These elastic tabs are nice, but they\&#8217;re going to clash with indentation in some cases. (The first code sample rely on proper indentation which did not work with the live preview, let\&#8217;s hope it will work once submitted.) Here is a big regular expressions comming from PHP Markdown for which this particular kind of indentation won\&#8217;t work (unless you insert a lot of blank lines):</p>
<pre><code>$text = preg_replace(\'{
        (                         # $1: Marker
            (?&lt; !\\*\\*) \\*\\* |   #     (not preceded by two chars of
            (?&lt;!__)   __       #      the same marker)
        )
        (?=\\S)                    # Not followed by whitespace
        (?!\\1)                    #   or two others marker chars.
        (                         # $2: Content
            (?:
                [^*_]+?           # Anthing not em markers.
            |
                                  # Balence any regular emphasis inside.
            ([*_]) (?=\\S) .+? (?&lt;=\\S) \\3    # $3: em char (* or _)
            |
                (?! \\1 ) .        # Allow unbalenced * and _.
            )+?
        )
        (?&lt;=\\S) \\1             # End mark not preceded by whitespace.
    }sx\',
    \'<strong>\\2\', $text);</strong></code></pre>
<p>And even with inserted blank lines it\&#8217;s never going to solve something like this either:</p>
<pre><code>$conversion_table = array(
    \'a\' => array(\'à\',\'â\',\'á\',\'ä\',\'ã\'),
    \'e\' => array(\'è\',\'ê\',\'é\',\'ë\'    ),
    \'i\' => array(\'ì\',\'î\',\'í\',\'ï\'    ),
    \'n\' => array(                \'ñ\'),
    \'o\' => array(\'ò\',\'ô\',\'ó\',\'ö\',\'õ\'),
    \'u\' => array(\'ù\',\'û\',\'ú\',\'ü\'    ),
    \'y\' => array(            \'ÿ\'    ),
    );</code></pre>
<p>But for both code samples, I suppose a different layout could be used, maybe it would be less pretty but it would still work, while the rest of the code benefits from elastic tabs. But while it wouldn\&#8217;t work everywhere, I have to admit I like the idea of elastic tabs. It could be a real time-saver.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kussmaul</title>
		<link>http://www.red-sweater.com/blog/154/elastic-tabs/comment-page-1#comment-8563</link>
		<dc:creator>Michael Kussmaul</dc:creator>
		<pubDate>Tue, 04 Jul 2006 09:40:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/154/elastic-tabs#comment-8563</guid>
		<description>I&#039;m always wondering, when the 50-years old way of source-code formating finally goes away... My dream-source-code-editor would adding embedded pictures, sticky-notes, etc (much like more modern word processors, like Pages, Word, etc). How often had I to ASCII-draw message-flows into source-code, instead of simply embedding a nice picture, or adding a collapsable sticky-note, instead of spoiling the source-code with 10+ lines of extensive comments...

It seems all current editors are still focused on 80-line text and cryptic handling of comments (adding // */, etc) - I hope the day will come, when this will finally change :-) Not everyone likes EMACS, VI for coding, I want a nice GUI, which also offers the benefits of a GUI :-)</description>
		<content:encoded><![CDATA[<p>I&#8217;m always wondering, when the 50-years old way of source-code formating finally goes away&#8230; My dream-source-code-editor would adding embedded pictures, sticky-notes, etc (much like more modern word processors, like Pages, Word, etc). How often had I to ASCII-draw message-flows into source-code, instead of simply embedding a nice picture, or adding a collapsable sticky-note, instead of spoiling the source-code with 10+ lines of extensive comments&#8230;</p>
<p>It seems all current editors are still focused on 80-line text and cryptic handling of comments (adding // */, etc) &#8211; I hope the day will come, when this will finally change :-) Not everyone likes EMACS, VI for coding, I want a nice GUI, which also offers the benefits of a GUI :-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
