<?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: S5 1.1a1</title>
	<atom:link href="http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/feed/" rel="self" type="application/rss+xml" />
	<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/</link>
	<description>Things that Eric A. Meyer, CSS expert, writes about on his personal Web site; it&#039;s largely Web standards and Web technology, but also various bits of culture, politics, personal observations, and other miscellaneous stuff</description>
	<lastBuildDate>Tue, 18 Jun 2013 15:30:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Eric</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1784</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Wed, 10 Nov 2004 16:50:13 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1784</guid>
		<description><![CDATA[Micha&#235;l: Thanks.  That&#039;s right along the lines I was considering, but hadn&#039;t yet managed to figure out how to make work.  I&#039;ll be working on adding your code today, along with some suggested code from the 1.0 days that didn&#039;t make it into the final version.

L: I tried viewing the testbed file in a 640x480 window and the text was still quite readable, so I&#039;m not sure why it turned out too small for you.  As for the controls exceeding the footer at smaller font sizes, that would appear to be a fault in the theme&#039;s CSS, one that wasn&#039;t revealed until the scaling routines were added.  I&#039;ll worry about that part later.]]></description>
		<content:encoded><![CDATA[<p>Micha&euml;l: Thanks.  That&#8217;s right along the lines I was considering, but hadn&#8217;t yet managed to figure out how to make work.  I&#8217;ll be working on adding your code today, along with some suggested code from the 1.0 days that didn&#8217;t make it into the final version.</p>
<p>L: I tried viewing the testbed file in a 640&#215;480 window and the text was still quite readable, so I&#8217;m not sure why it turned out too small for you.  As for the controls exceeding the footer at smaller font sizes, that would appear to be a fault in the theme&#8217;s CSS, one that wasn&#8217;t revealed until the scaling routines were added.  I&#8217;ll worry about that part later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: L Rutker</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1783</link>
		<dc:creator>L Rutker</dc:creator>
		<pubDate>Wed, 10 Nov 2004 15:32:08 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1783</guid>
		<description><![CDATA[Fonts scale down to small with small viewports. Remember that some projectors are 640x480. On viewports with a height of less than 452 (might be 451px) the ø, &lt; &lt; and &gt;&gt; display improperly.
Tested in FF 1.0 and IE6 on Windows.]]></description>
		<content:encoded><![CDATA[<p>Fonts scale down to small with small viewports. Remember that some projectors are 640&#215;480. On viewports with a height of less than 452 (might be 451px) the ø, < < and >> display improperly.<br />
Tested in FF 1.0 and IE6 on Windows.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micha</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1781</link>
		<dc:creator>Micha</dc:creator>
		<pubDate>Wed, 10 Nov 2004 13:09:21 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1781</guid>
		<description><![CDATA[Eric, here&#039;s a refactoring of your font scaling code that solves the IE5/Mac problem you spotted and doesn&#039;t add stylesheets ad infinitum:

&lt;code&gt;
function fontSize(value)
{
   if (!isIE) {
      var obj = document.getElementsByTagName(&#039;body&#039;)[0];
      obj.style.fontSize = value;
   } else {
      if (&#039;undefined&#039; == document[&#039;s5ss&#039;] + &#039;&#039;) {
         document.createStyleSheet();
         document.s5ss = document.styleSheets[document.styleSheets.length - 1];
      }
      document.s5ss.addRule(&#039;body&#039;,&#039;font-size: &#039; + value + &#039; !important;&#039;);
   }
}

function fontZero() {
   fontSize(&#039;1em&#039;);
}

function fontScale() {
  ... 
  var newSize = Math.min(Math.round(vSize/vScale),Math.round(hSize/hScale));
   fontSize(newSize + &#039;px&#039;);
}
&lt;/code&gt;

However when resizing the window several times in a short timespan, I noticed it would sometimes miscalculate the font size. Maybe IE5/Mac needs a few microseconds to update the current window dimension properties (?!).]]></description>
		<content:encoded><![CDATA[<p>Eric, here&#8217;s a refactoring of your font scaling code that solves the IE5/Mac problem you spotted and doesn&#8217;t add stylesheets ad infinitum:</p>
<p><code><br />
function fontSize(value)<br />
{<br />
   if (!isIE) {<br />
      var obj = document.getElementsByTagName('body')[0];<br />
      obj.style.fontSize = value;<br />
   } else {<br />
      if ('undefined' == document['s5ss'] + '') {<br />
         document.createStyleSheet();<br />
         document.s5ss = document.styleSheets[document.styleSheets.length - 1];<br />
      }<br />
      document.s5ss.addRule('body','font-size: ' + value + ' !important;');<br />
   }<br />
}</p>
<p>function fontZero() {<br />
   fontSize('1em');<br />
}</p>
<p>function fontScale() {<br />
  ...<br />
  var newSize = Math.min(Math.round(vSize/vScale),Math.round(hSize/hScale));<br />
   fontSize(newSize + 'px');<br />
}<br />
</code></p>
<p>However when resizing the window several times in a short timespan, I noticed it would sometimes miscalculate the font size. Maybe IE5/Mac needs a few microseconds to update the current window dimension properties (?!).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1759</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Wed, 10 Nov 2004 02:35:54 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1759</guid>
		<description><![CDATA[Matt: Found and fixed the problem-- my code didn&#039;t cover all cases of toggling between the outline and slide views.  Thanks!]]></description>
		<content:encoded><![CDATA[<p>Matt: Found and fixed the problem&#8211; my code didn&#8217;t cover all cases of toggling between the outline and slide views.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt O'Dell</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1737</link>
		<dc:creator>Matt O'Dell</dc:creator>
		<pubDate>Tue, 09 Nov 2004 19:56:25 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1737</guid>
		<description><![CDATA[I just sent you a screen grab of the browser window. I&#039;m using Firefox 1.0PR]]></description>
		<content:encoded><![CDATA[<p>I just sent you a screen grab of the browser window. I&#8217;m using Firefox 1.0PR</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1734</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Tue, 09 Nov 2004 19:40:23 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1734</guid>
		<description><![CDATA[Matt: In what browser?  I don&#039;t see the same thing happening in my tests.]]></description>
		<content:encoded><![CDATA[<p>Matt: In what browser?  I don&#8217;t see the same thing happening in my tests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt O'Dell</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1730</link>
		<dc:creator>Matt O'Dell</dc:creator>
		<pubDate>Tue, 09 Nov 2004 19:36:19 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1730</guid>
		<description><![CDATA[By the way, I was taking a look at your slide presentation, and you must have just recently added the outline CSS file to make the outline look pretty also. Unfortunately the h1 border element is transfering to the slide show presentation, therefore placing it a 2 pixels out of the top section. Just FYI]]></description>
		<content:encoded><![CDATA[<p>By the way, I was taking a look at your slide presentation, and you must have just recently added the outline CSS file to make the outline look pretty also. Unfortunately the h1 border element is transfering to the slide show presentation, therefore placing it a 2 pixels out of the top section. Just FYI</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1724</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Tue, 09 Nov 2004 16:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1724</guid>
		<description><![CDATA[I implemented Mook&#039;s suggestion of flipping the &lt;code&gt;body&lt;/code&gt;&#039;s &lt;code&gt;display&lt;/code&gt; to &lt;code&gt;none&lt;/code&gt; and back to &lt;code&gt;block&lt;/code&gt;, and that seems to have done the trick.  There&#039;s a brief flicker after resizing, but it&#039;s nothing to get upset about for the moment.   For now, a fix has been demonstrated, and that&#039;s good enough.  Later, I can root around for other style changes that will cause the same effect sans blink.  If that hunt fails, I&#039;ll accept the blink.

The various suggestions of forcing a reload didn&#039;t work out because the font scaling, which is fired by a &lt;code&gt;window.onresize&lt;/code&gt; event, was what had to do a &lt;code&gt;history.go(0)&lt;/code&gt; call in order to trigger the reflow.  But a reload is interpreted as a resize, so an infinite loop of reloading was set up where the reload fired an onresize event, which ran the scaling code, which fired a reload, which...

Ben: a big part of this is to make the process transparent, and to work in all supported browsers.  IE/Win, for example, doesn&#039;t allow font scaling if the font size is set in pixels, as I expect will happen with many themes.  In fact, the only reason the keyboard text-scale function worked is that the intro slide show&#039;s theme sets the body font size in pixels, and everything else in ems or percentages, and you were using a Gecko browser.  A theme that did a lot of font setting and element sizing in pixels would scale badly, whether via the keyboard or the scaling routine I&#039;ve created.

Micha&#235;l: I&#039;m not so concerned about adding rules ad infinitum; some of the existing code already does that.  I also don&#039;t expect users to do a lot of resizing of the window-- none at all, actually, in 99% of cases.  The major point of this is to allow dynamic rescaling if the target resolution isn&#039;t what the theme author expected, so that if your 1024x768 show ends up in an 800x600 environment, the slides should at least be readable.]]></description>
		<content:encoded><![CDATA[<p>I implemented Mook&#8217;s suggestion of flipping the <code>body</code>&#8216;s <code>display</code> to <code>none</code> and back to <code>block</code>, and that seems to have done the trick.  There&#8217;s a brief flicker after resizing, but it&#8217;s nothing to get upset about for the moment.   For now, a fix has been demonstrated, and that&#8217;s good enough.  Later, I can root around for other style changes that will cause the same effect sans blink.  If that hunt fails, I&#8217;ll accept the blink.</p>
<p>The various suggestions of forcing a reload didn&#8217;t work out because the font scaling, which is fired by a <code>window.onresize</code> event, was what had to do a <code>history.go(0)</code> call in order to trigger the reflow.  But a reload is interpreted as a resize, so an infinite loop of reloading was set up where the reload fired an onresize event, which ran the scaling code, which fired a reload, which&#8230;</p>
<p>Ben: a big part of this is to make the process transparent, and to work in all supported browsers.  IE/Win, for example, doesn&#8217;t allow font scaling if the font size is set in pixels, as I expect will happen with many themes.  In fact, the only reason the keyboard text-scale function worked is that the intro slide show&#8217;s theme sets the body font size in pixels, and everything else in ems or percentages, and you were using a Gecko browser.  A theme that did a lot of font setting and element sizing in pixels would scale badly, whether via the keyboard or the scaling routine I&#8217;ve created.</p>
<p>Micha&euml;l: I&#8217;m not so concerned about adding rules ad infinitum; some of the existing code already does that.  I also don&#8217;t expect users to do a lot of resizing of the window&#8211; none at all, actually, in 99% of cases.  The major point of this is to allow dynamic rescaling if the target resolution isn&#8217;t what the theme author expected, so that if your 1024&#215;768 show ends up in an 800&#215;600 environment, the slides should at least be readable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Guitton</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1717</link>
		<dc:creator>Michael Guitton</dc:creator>
		<pubDate>Tue, 09 Nov 2004 10:17:29 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1717</guid>
		<description><![CDATA[Eric, I found the code snippet which doesn&#039;t work in IE5/Mac:

&lt;code&gt;var ss = document.styleSheets[1];
		ss.addRule(...);&lt;/code&gt;

in &lt;code&gt;FontZero()&lt;/code&gt; and &lt;code&gt;FontScale()&lt;/code&gt; subroutines.

If you write something like:

&lt;code&gt;document.createStyleSheet();
document.styleSheets[document.styleSheets.length - 1].addRule(&#039;body&#039;,&#039;font-size: &#039; + newSize + &#039;px !important;&#039;);&lt;/code&gt;

... it works back again (?!). This is kind of puzzling. In this particular CSS configuration, it seems IE/Mac fails to add rules to an existing style sheet.

Of course, you wouldn&#039;t want to add styles sheets ad infinitum so we&#039;ll need to figure a way to add and remove rules from the dynamic stylesheet we just created. I&#039;m a little busy right now so I&#039;ll come later on this topic unless someone would write the necessary glue code for IE/Mac.]]></description>
		<content:encoded><![CDATA[<p>Eric, I found the code snippet which doesn&#8217;t work in IE5/Mac:</p>
<p><code>var ss = document.styleSheets[1];<br />
		ss.addRule(...);</code></p>
<p>in <code>FontZero()</code> and <code>FontScale()</code> subroutines.</p>
<p>If you write something like:</p>
<p><code>document.createStyleSheet();<br />
document.styleSheets[document.styleSheets.length - 1].addRule('body','font-size: ' + newSize + 'px !important;');</code></p>
<p>&#8230; it works back again (?!). This is kind of puzzling. In this particular CSS configuration, it seems IE/Mac fails to add rules to an existing style sheet.</p>
<p>Of course, you wouldn&#8217;t want to add styles sheets ad infinitum so we&#8217;ll need to figure a way to add and remove rules from the dynamic stylesheet we just created. I&#8217;m a little busy right now so I&#8217;ll come later on this topic unless someone would write the necessary glue code for IE/Mac.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micha</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1716</link>
		<dc:creator>Micha</dc:creator>
		<pubDate>Tue, 09 Nov 2004 09:26:56 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1716</guid>
		<description><![CDATA[Regarding Gecko&#039;s &quot;bug&quot;, I&#039;d suggest to try the old NS4 &lt;code&gt;window.history.go(0)&lt;/code&gt; trick as &lt;a href=&quot;http://www.meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1709&quot;&gt;jgraham&lt;/a&gt; did. If it doesn&#039;t work, maybe you should implement a rudimendary style switcher to set predefined font sizes upon resize events (?) The style sheets would then be triggered when window inner witdh and height would met a given fence (e.g. 800x600, 1024x768, 1280x1024, 1600x1200, etc.)]]></description>
		<content:encoded><![CDATA[<p>Regarding Gecko&#8217;s &#8220;bug&#8221;, I&#8217;d suggest to try the old NS4 <code>window.history.go(0)</code> trick as <a href="http://www.meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1709">jgraham</a> did. If it doesn&#8217;t work, maybe you should implement a rudimendary style switcher to set predefined font sizes upon resize events (?) The style sheets would then be triggered when window inner witdh and height would met a given fence (e.g. 800&#215;600, 1024&#215;768, 1280&#215;1024, 1600&#215;1200, etc.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christoph Wagner</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1712</link>
		<dc:creator>Christoph Wagner</dc:creator>
		<pubDate>Mon, 08 Nov 2004 16:38:06 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1712</guid>
		<description><![CDATA[And a, uhm, wordpress bug here:
&lt;code&gt;Warning: Compilation failed: nothing to repeat at offset 0 in /home/httpd/vhosts/meyerweb.com/httpdocs/eric/thoughts/wp-includes/functions.php on line 1357&lt;/code&gt;

&lt;code&gt;Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/meyerweb.com/httpdocs/eric/thoughts/wp-includes/functions.php:1353) in /home/httpd/vhosts/meyerweb.com/httpdocs/eric/thoughts/wp-comments-post.php on line 89&lt;/code&gt;

I get alot of these on a blank page when posting a comment.]]></description>
		<content:encoded><![CDATA[<p>And a, uhm, wordpress bug here:<br />
<code>Warning: Compilation failed: nothing to repeat at offset 0 in /home/httpd/vhosts/meyerweb.com/httpdocs/eric/thoughts/wp-includes/functions.php on line 1357</code></p>
<p><code>Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/meyerweb.com/httpdocs/eric/thoughts/wp-includes/functions.php:1353) in /home/httpd/vhosts/meyerweb.com/httpdocs/eric/thoughts/wp-comments-post.php on line 89</code></p>
<p>I get alot of these on a blank page when posting a comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christoph Wagner</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1711</link>
		<dc:creator>Christoph Wagner</dc:creator>
		<pubDate>Mon, 08 Nov 2004 16:36:28 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1711</guid>
		<description><![CDATA[Well, i think its bad, that if i resize to 800*600 I can&#039;t read the whole text, because it&#039;s covered by the slide&#039;s title.
Firefox 1.0 RC2 on Windows
But keep the nice work going!]]></description>
		<content:encoded><![CDATA[<p>Well, i think its bad, that if i resize to 800*600 I can&#8217;t read the whole text, because it&#8217;s covered by the slide&#8217;s title.<br />
Firefox 1.0 RC2 on Windows<br />
But keep the nice work going!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jgraham</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1709</link>
		<dc:creator>jgraham</dc:creator>
		<pubDate>Mon, 08 Nov 2004 15:38:53 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1709</guid>
		<description><![CDATA[If you want to hack around gecko bugs you might be able to take advantage of https://bugzilla.mozilla.org/show_bug.cgi?id=258917. If you call something like &lt;code&gt;history.go(0)&lt;/code&gt; in an &lt;code&gt;onresize&lt;/code&gt; handler the display will be redrawn but otherwise nothing will happen. Of course it&#039;s better to avoid this if possible...]]></description>
		<content:encoded><![CDATA[<p>If you want to hack around gecko bugs you might be able to take advantage of <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=258917" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=258917</a>. If you call something like <code>history.go(0)</code> in an <code>onresize</code> handler the display will be redrawn but otherwise nothing will happen. Of course it&#8217;s better to avoid this if possible&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Ward</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1707</link>
		<dc:creator>Ben Ward</dc:creator>
		<pubDate>Mon, 08 Nov 2004 13:32:49 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1707</guid>
		<description><![CDATA[I&#039;m actually a little curious about the &#039;text scaling&#039; bug. I started playing with s5 a week ago but found that text could be comfortably scaled by just using the browser (Firefox) text resize functionality.

Is the aim of this bug to make that process completely transparent and automatic so as to avoid minor manual labour like this? Or is the bug actually something much larger that I&#039;ve missed?

As regards image scaling: Why not leave that up to the author? Including some classes that can be added to images for dynamic sizing with height or width as 90% (for instance) and allow the browser handle the aspect automatically.

I&#039;m extremely impressed with everything so far though, and look forward to the progress. Here&#039;s to free time!]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m actually a little curious about the &#8216;text scaling&#8217; bug. I started playing with s5 a week ago but found that text could be comfortably scaled by just using the browser (Firefox) text resize functionality.</p>
<p>Is the aim of this bug to make that process completely transparent and automatic so as to avoid minor manual labour like this? Or is the bug actually something much larger that I&#8217;ve missed?</p>
<p>As regards image scaling: Why not leave that up to the author? Including some classes that can be added to images for dynamic sizing with height or width as 90% (for instance) and allow the browser handle the aspect automatically.</p>
<p>I&#8217;m extremely impressed with everything so far though, and look forward to the progress. Here&#8217;s to free time!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Clarkson</title>
		<link>http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1706</link>
		<dc:creator>Ken Clarkson</dc:creator>
		<pubDate>Mon, 08 Nov 2004 12:50:13 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/2004/11/07/s5-11a1/#comment-1706</guid>
		<description><![CDATA[I&#039;d like to use a package like this for presentations that include SVG, under Firefox only if that&#039;s the only way it can be done; it&#039;s then possible to include little live demos within the slides, using  some javascript and possibly XBL.  I haven&#039;t had any luck getting SVG to display when simply included in html, but it doesn&#039;t seem to take too much (replacement of two innerHTML() calls, mainly) to apply S5 to xml.  I&#039;m groping pretty blindly on this, so any suggestions appreciated.

Also: am I alone in wanting a print version that looks pretty much like the slideshow version?]]></description>
		<content:encoded><![CDATA[<p>I&#8217;d like to use a package like this for presentations that include SVG, under Firefox only if that&#8217;s the only way it can be done; it&#8217;s then possible to include little live demos within the slides, using  some javascript and possibly XBL.  I haven&#8217;t had any luck getting SVG to display when simply included in html, but it doesn&#8217;t seem to take too much (replacement of two innerHTML() calls, mainly) to apply S5 to xml.  I&#8217;m groping pretty blindly on this, so any suggestions appreciated.</p>
<p>Also: am I alone in wanting a print version that looks pretty much like the slideshow version?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->