<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Wouldn&#8217;t it be nice?</title>
	<link>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/</link>
	<description>It&#8217;s a work in progress</description>
	<pubDate>Fri, 25 Jul 2008 12:26:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: Ben Buchanan</title>
		<link>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11965</link>
		<pubDate>Mon, 08 Oct 2007 06:16:52 +0000</pubDate>
		<guid>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11965</guid>
					<description>Although not top of my wish list, I can certainly see where this would be useful.</description>
		<content:encoded><![CDATA[<p>Although not top of my wish list, I can certainly see where this would be useful.
</p>]]></content:encoded>
				</item>
	<item>
		<title>by: InfinitFocus</title>
		<link>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11786</link>
		<pubDate>Mon, 27 Aug 2007 20:48:18 +0000</pubDate>
		<guid>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11786</guid>
					<description>I love the idea.... As a designer you're no longer limited to boring CSS layouts....  Dynamic menus are all the same... With this I can have a menu placed in the lower right corner at a 45 degree angle... Just Because I want it there...

And you're right Adobe uses it... Quark uses it...  Why shouldn't the WEB!!!  It's such a basic function in all programs... Why is it so hard to implement in CSS...  

Has anyone even bothered asking Adobe, Quark, or Microsoft if they would open source that basic code to the browser companies????  Why wouldn't they?  Adobe Products are basically for designers... If that's the case wouldn't they want their customers to be able to produce the best web design as possible???

Some things should be standard.  And this is one of those things....

Keep pushing for it please...</description>
		<content:encoded><![CDATA[<p>I love the idea&#8230;. As a designer you&#8217;re no longer limited to boring <abbr title="Cascading Style Sheets">CSS</abbr> layouts&#8230;.  Dynamic menus are all the same&#8230; With this I can have a menu placed in the lower right corner at a 45 degree angle&#8230; Just Because I want it there&#8230;</p>
<p>And you&#8217;re right Adobe uses it&#8230; Quark uses it&#8230;  Why shouldn&#8217;t the WEB!!!  It&#8217;s such a basic function in all programs&#8230; Why is it so hard to implement in <abbr title="Cascading Style Sheets">CSS</abbr>&#8230;  </p>
<p>Has anyone even bothered asking Adobe, Quark, or Microsoft if they would open source that basic code to the browser companies????  Why wouldn&#8217;t they?  Adobe Products are basically for designers&#8230; If that&#8217;s the case wouldn&#8217;t they want their customers to be able to produce the best web design as possible???</p>
<p>Some things should be standard.  And this is one of those things&#8230;.</p>
<p>Keep pushing for it please&#8230;
</p>]]></content:encoded>
				</item>
	<item>
		<title>by: Andrew</title>
		<link>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11534</link>
		<pubDate>Thu, 12 Jul 2007 13:44:48 +0000</pubDate>
		<guid>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11534</guid>
					<description>Its certainly a great start. Opens up some real creative possibilities for designers. I look on with interest.</description>
		<content:encoded><![CDATA[<p>Its certainly a great start. Opens up some real creative possibilities for designers. I look on with interest.
</p>]]></content:encoded>
				</item>
	<item>
		<title>by: michael stuhr</title>
		<link>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11485</link>
		<pubDate>Wed, 04 Jul 2007 11:32:12 +0000</pubDate>
		<guid>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11485</guid>
					<description>I once said &quot;wouldn't it be cool if every browser would support multi-column layout, I mean not only for p's?&quot; and then came IE 7 and I realized that we should pray for other things first.</description>
		<content:encoded><![CDATA[<p>I once said &#8220;wouldn&#8217;t it be cool if every browser would support multi-column layout, I mean not only for p&#8217;s?&#8221; and then came <abbr title="Internet Explorer">IE</abbr> 7 and I realized that we should pray for other things first.
</p>]]></content:encoded>
				</item>
	<item>
		<title>by: CSS Working Group Blog</title>
		<link>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11484</link>
		<pubDate>Tue, 03 Jul 2007 23:19:52 +0000</pubDate>
		<guid>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11484</guid>
					<description>[...] Aaron Gustafson asked last week in an article called  “Wouldn't it be nice?” for rotation of text over arbitrary angles and for wrapping text around non-rectangular floating images. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Aaron Gustafson asked last week in an article called  “Wouldn&#8217;t it be nice?” for rotation of text over arbitrary angles and for wrapping text around non-rectangular floating images. [&#8230;]
</p>]]></content:encoded>
				</item>
	<item>
		<title>by: Tomas Caspers</title>
		<link>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11482</link>
		<pubDate>Sun, 01 Jul 2007 09:38:28 +0000</pubDate>
		<guid>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11482</guid>
					<description>What would aliased text look like in any box that is not rotated in right angles?</description>
		<content:encoded><![CDATA[<p>What would aliased text look like in any box that is not rotated in right angles?
</p>]]></content:encoded>
				</item>
	<item>
		<title>by: Aaron</title>
		<link>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11481</link>
		<pubDate>Thu, 28 Jun 2007 19:51:58 +0000</pubDate>
		<guid>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11481</guid>
					<description>&lt;strong&gt;Jason:&lt;/strong&gt; That was my initial inclination, but I was a little concerned that it might be confusing in practice. That said, I would be against them offering multiple ways of indicating it like they do with backgrounds.</description>
		<content:encoded><![CDATA[<p><strong>Jason:</strong> That was my initial inclination, but I was a little concerned that it might be confusing in practice. That said, I would be against them offering multiple ways of indicating it like they do with backgrounds.
</p>]]></content:encoded>
				</item>
	<item>
		<title>by: Jason Querido</title>
		<link>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11480</link>
		<pubDate>Thu, 28 Jun 2007 15:12:25 +0000</pubDate>
		<guid>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11480</guid>
					<description>WRT the anchor, I wonder if offset coordinates could be also used in place of the words, similar to positioning background images.
e.g. &quot;0px 0px&quot; instead of &quot;top left&quot;</description>
		<content:encoded><![CDATA[<p>WRT the anchor, I wonder if offset coordinates could be also used in place of the words, similar to positioning background images.<br />
e.g. &#8220;0px 0px&#8221; instead of &#8220;top left&#8221;
</p>]]></content:encoded>
				</item>
	<item>
		<title>by: Aaron</title>
		<link>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11479</link>
		<pubDate>Thu, 28 Jun 2007 14:56:01 +0000</pubDate>
		<guid>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11479</guid>
					<description>Good catch on the floating thing, Porter (and Jonathan). I meant to have a &lt;code&gt;float&lt;/code&gt; rule in the example. As for the rotation while floating, that's a good point. I'm trying to recall what my thought process was at the time... I believe my initial desire was to see rotation based on the &lt;code&gt;rotation-anchor&lt;/code&gt; property (i.e. if rotated from the top left corner, rotation would be up and left from there if negative; if from the center, it would rotate around the center). It is a tricky thing for sure, especially when you begin to consider the bounding box, as Jonathan brings up. I think this is something we need to talk more about. Should an element's box rotate with the element, or should it act kinda like relative positioning and leave its box untouched? That's where the polygonal margins would come in handy.

Back to &lt;code&gt;rotation-anchor&lt;/code&gt; for a moment, I would argue very much in favor of that property because it can be a very useful tool for precise rotation of an object. Yes, it does introduce some crazy math for calculating and laying out images and such, but programs like Photoshop and Quark have been doing this for years.

As for the polygonal margins, I understand where you're coming from Kevin, but this is also the sort of thing which has been done for years in Quark, Pagemaker, and InDesign. It can't be rocket science. Perhaps a member of the W3C might even be willing to open source the calculations to allow browser vendors to implement it more easily. Plus, If we are already considering more involved layouts and text flows with the Advanced Layout Module in CSS 3, it seems only reasonable to add this option as well. Otherwise, I imagine folks will start to corrupt Advanced Layout make it work (return of the spacer GIF, anyone?).

By no means am I assuming these ideas are perfect, but I'd like to see the folks on the ground discussing these sorts of enhancements more (rather than just leaving it to the folks at the W3C). I think to some degree, we should be letting them know what we want and how we'd like to see it implemented.

Thank you all for your comments. Keep 'em coming!</description>
		<content:encoded><![CDATA[<p>Good catch on the floating thing, Porter (and Jonathan). I meant to have a <code>float</code> rule in the example. As for the rotation while floating, that&#8217;s a good point. I&#8217;m trying to recall what my thought process was at the time&#8230; I believe my initial desire was to see rotation based on the <code>rotation-anchor</code> property (i.e. if rotated from the top left corner, rotation would be up and left from there if negative; if from the center, it would rotate around the center). It is a tricky thing for sure, especially when you begin to consider the bounding box, as Jonathan brings up. I think this is something we need to talk more about. Should an element&#8217;s box rotate with the element, or should it act kinda like relative positioning and leave its box untouched? That&#8217;s where the polygonal margins would come in handy.</p>
<p>Back to <code>rotation-anchor</code> for a moment, I would argue very much in favor of that property because it can be a very useful tool for precise rotation of an object. Yes, it does introduce some crazy math for calculating and laying out images and such, but programs like Photoshop and Quark have been doing this for years.</p>
<p>As for the polygonal margins, I understand where you&#8217;re coming from Kevin, but this is also the sort of thing which has been done for years in Quark, Pagemaker, and InDesign. It can&#8217;t be rocket science. Perhaps a member of the <abbr title="World Wide Web Consortium">W3C</abbr> might even be willing to open source the calculations to allow browser vendors to implement it more easily. Plus, If we are already considering more involved layouts and text flows with the Advanced Layout Module in <abbr title="Cascading Style Sheets">CSS</abbr> 3, it seems only reasonable to add this option as well. Otherwise, I imagine folks will start to corrupt Advanced Layout make it work (return of the spacer GIF, anyone?).</p>
<p>By no means am I assuming these ideas are perfect, but I&#8217;d like to see the folks on the ground discussing these sorts of enhancements more (rather than just leaving it to the folks at the <abbr title="World Wide Web Consortium">W3C</abbr>). I think to some degree, we should be letting them know what we want and how we&#8217;d like to see it implemented.</p>
<p>Thank you all for your comments. Keep &#8216;em coming!
</p>]]></content:encoded>
				</item>
	<item>
		<title>by: Malarkey</title>
		<link>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11478</link>
		<pubDate>Thu, 28 Jun 2007 13:41:10 +0000</pubDate>
		<guid>http://www.easy-reader.net/archives/2007/06/27/wouldnt-it-be-nice/#comment-11478</guid>
					<description>As I said to you when I first saw this in January, I think that your ideas have real legs and I hope that the CSS WG give them the attention they deserve as they would help designers using CSS a great deal.

I also think that your considered approach to suggesting additions and new specifications is exactly the right one. Very cool work mate!</description>
		<content:encoded><![CDATA[<p>As I said to you when I first saw this in January, I think that your ideas have real legs and I hope that the <abbr title="Cascading Style Sheets">CSS</abbr> WG give them the attention they deserve as they would help designers using <abbr title="Cascading Style Sheets">CSS</abbr> a great deal.</p>
<p>I also think that your considered approach to suggesting additions and new specifications is exactly the right one. Very cool work mate!
</p>]]></content:encoded>
				</item>
</channel>
</rss>
