<?xml version="1.0" encoding="ISO-8859-1"?><!-- OPML generated by Radio UserLand v8.0.8 on Thu, 20 Jun 2002 00:33:50 GMT -->
<opml version="1.1">	<head>		<title>opmlRender.opml</title>		<dateCreated>Sun, 28 Apr 2002 00:21:24 GMT</dateCreated>		<dateModified>Thu, 20 Jun 2002 00:33:49 GMT</dateModified>		<ownerName>Marc Barrot</ownerName>		<ownerEmail>mbarrot@dig.fr</ownerEmail>		<expansionState>4, 6, 8, 11, 14, 16, 19, 20, 22, 25, 27, 29, 31, 34, 36, 39, 42, 43, 45, 47, 49</expansionState>		<vertScrollState>1</vertScrollState>		<windowTop>66</windowTop>		<windowLeft>439</windowLeft>		<windowBottom>662</windowBottom>		<windowRight>1027</windowRight>		</head>	<body>		<outline text="#title &quot;opmlRender&quot;"/>		<outline text="#opmlStory &quot;http://radio.weblogs.com/0104487/gems/opml/opmlRender.opml&quot;"/>		<outline text="#renderOutlineWith &quot;activeRenderer&quot;"/>		<outline text="What is opmlRender ?">			<outline text="opmlRender is a &lt;a href=&quot;http://frontier.userland.com/stories/storyReader$1047&quot;&gt;UserTalk&lt;/a&gt; macro command that renders, or translates, an &lt;a href=&quot;http://www.opml.org/&quot;&gt;OPML&lt;/a&gt; outline into HTML."/>			</outline>		<outline text="Why use it at all ?">			<outline text="I find it easier to manage some of the content published in a Radio weblog as outline files."/>			<outline text="Some of those outlines are rendered directly in &lt;b&gt;s l a m&lt;/b&gt; 's #homeTemplate file.">				<outline text="The &lt;a href=&quot;http://radio.weblogs.com/0104487/gems/opml/headlines.opml&quot;&gt;headlines&lt;/a&gt;, &lt;a href=&quot;http://radio.weblogs.com/0104487/gems/opml/navsection.opml&quot;&gt;home&lt;/a&gt;, &lt;a href=&quot;http://radio.weblogs.com/0104487/gems/opml/tracks.opml&quot;&gt;tracks&lt;/a&gt; and &lt;a href=&quot;http://radio.weblogs.com/0104487/gems/opml/resources.opml&quot;&gt;resources&lt;/a&gt; sections for instance, are all outlines."/>				<outline text="I created those outlines directly in Radio, and saved them as opml documents (Radio's default format for external outlines)."/>				</outline>			</outline>		<outline text="Installing opmlRender.">			<outline text="Simple enough, just save a copy of opmlRender as a &lt;a href=&quot;http://radio.weblogs.com/0104487/gems/code/opmlRender.txt&quot; target=&quot;_blank&quot;&gt;text file&lt;/a&gt; in your Radio application Macros folder."/>			<outline text="If you're a user of activeRenderer, opmlRender is part of the tool, it is already installed. Neat uh ?"/>			</outline>		<outline text="How does it work ?">			<outline text="Insert &amp;lt;% opmlRender ( &quot;url&quot; ) %&amp;gt; anywhere you want the &quot;url&quot; outline to be rendered."/>			<outline text="&quot;url&quot; must be a regularly formed &lt;a href=&quot;http://www.info.apple.com/help/knowledgebase/def/url.html&quot;&gt;uniform resource locator&lt;/a&gt; for the outline to render.">				<outline text="A local url uses the file:// header. It could be something like: file:///C/Program%20files/Radio%20UserLand/www/instantOutliner/yourOutline.opml."/>				<outline text="A remote url uses the http:// header. As in http://radio.weblogs.com/0104487/instantOutliner/marcBarrot.opml."/>				</outline>			<outline text="The style of the html that opmlRender outputs can be customized using &lt;a href=&quot;http://www.w3.org/Style/CSS/&quot;&gt;Cascading Style Sheets&lt;/a&gt;.">				<outline text="Every node in the outline is rendered in a paragraph with a CSS class attribute.">					<outline text="The default class name used by opmlRender is &quot;l&quot; (lowercase l), a bit terse maybe :-)"/>					<outline text="You can substitude any other name by supplying a name string as the second argument to opmlRender.">						<outline text="For instance : &amp;lt;% opmlRender ( &quot;file:///Data/Marc/Radio%20UserLand/www/gems/opml/tracks.opml&quot;, &quot;track&quot; ) %&amp;gt;."/>						</outline>					<outline text="There's a catch: the string you supply, or the default &quot;l&quot; string, is not rendered directly as class=&quot;string&quot;."/>					<outline text="The macro adds a suffix, which is the level in the outline of the node being rendered. All outline summits are at level 1, their children are at level 2, and so on.">						<outline text="This very node of the opmlRender outline is rendered as a class=&quot;story5&quot; paragraph (I entered &amp;lt;% opmlRender ( &quot;file:///Data/Marc/Radio%20UserLand/www/gems/opml/opmlRender.opml&quot;, &quot;story&quot; ) %&amp;gt; in the story text for the html version of this tutorial - still with me :-) ?"/>						</outline>					</outline>				<outline text="You've got to provide for the matching CSS style definitions in the header part of the file where you insert opmlRender macros.">					<outline text="I  inserted the following line in the &amp;lt;header&amp;gt; section of the template for this (and all) stories:"/>					<outline text="&amp;lt;link rel=&quot;stylesheet&quot; type=&quot;text/css&quot; href=&quot;http://radio.weblogs.com/0104487/gems/css/stories.css&quot;&amp;gt;">						<outline text="The stories.css file is where all styling rules are specified."/>						</outline>					</outline>				</outline>			<outline text="It gets worse, you can specify an optional third parameter to opmlRender, that defines the way the outline is expanded before rendering.">				<outline text="If you do not specify a third parameter, or enter false (or 0), the outline is rendered as it was saved: collapsed nodes are not visible and skipped entirely in the rendered version."/>				<outline text="If you enter true, or 1, as third parameter, all the outline nodes are fully expanded before rendition."/>				</outline>			<outline text="The fourth and fifth optional parameters are specially useful if you've specified true as third argument.">				<outline text="I promise, those are the last ones :-)"/>				<outline text="The 4th optional argument is the maximum depth level rendered in the outline.">					<outline text=" It defaults to 0, no limit."/>					<outline text=" If an outline has a depth of 4 levels, but opmlRender's 4th argument is 2, all nodes of level 3 and 4 are ignored at rendering time."/>					</outline>				<outline text="The 5th optional argument is the maximum number of summit (level 1) nodes rendered in the outline.">					<outline text=" It defaults to 0, no limit as well."/>					<outline text=" If an outline includes 4 summits, but opmlRender's 5th argument is 2, only the first 2 summits and their children are rendered, the remaining 2 are ignored."/>					</outline>				</outline>			</outline>		<outline text="Some additional examples.">			<outline text="The headlines section at the top of &lt;b&gt;s l a m&lt;/b&gt; 's home page :">				<outline text="&amp;lt;% opmlRender ( &quot;file:///Data/Marc/Radio%20UserLand/www/gems/opml/headlines.opml&quot;, &quot;headline&quot;, true, 2, 1 ) %&amp;gt;"/>				</outline>			<outline text="The resources section in &lt;b&gt;s l a m&lt;/b&gt; 's home page :">				<outline text="&amp;lt;% opmlRender ( &quot;file:///Data/Marc/Radio%20UserLand/www/gems/opml/resources.opml&quot;, &quot;track&quot;, true, 3, 0 ) %&amp;gt;"/>				</outline>			<outline text="Dave Winer's instant outline, in HTML attire, why not :-)">				<outline text="&amp;lt;% opmlRender ( &quot;http://radio.weblogs.com/0001015/instantOutliner/daveWiner.opml&quot; ) %&amp;gt;"/>				</outline>			</outline>		<outline text="Credits">			<outline text="The opmlRender macro was born 'renderCss' quite some time ago."/>			<outline text="renderCss was based on some interesting work by &lt;a href=&quot;http://radio.weblogs.com/0100688/&quot;&gt;Carlos Granier&lt;/a&gt; and &lt;a href=&quot;http://radio.weblogs.com/0001017/&quot;&gt;Andy Fragen&lt;/a&gt;."/>			</outline>		</body>	</opml>