Home

About

Contents

Guidelines

Glossary

Contacts

Discussion

Recent Discussion

Create New Topic

Membership

Join Now

Login

Radio-Manila Outlining

For examples: http://iol3.uibk.ac.at/IOL/PlugIns/metaRendererBeispiele
user.html.renderers

bsoRenderer

• renders an outline created by siteTools.buildSiteOutline

• turns each line into a table.

• if level > 0, add an empty cell, with its width specified.

• width is a multiple of user.sitetools.indentpixels.

cadillac

• attempts to preserve absolutely the formatting of the outline on the docServerSite

fatHeadlines

• makes top-level headlines bold

• inserts paragraph tags between headlines

• indents headlines that are more than two levels deep

idealistRenderer

justText

• simplest of all outlines

• just gets the text of the outline

• no special rendering at allnewCulture

newCulture

• deletes comment lines and strips off end-of-line comments

• replaces empty lines with <p>s (skip a line to add space to the page)

• produce tab-indented text for the outlinenewSiteOutliner

notespagerenderer

pikeRenderer

• See rules below

prettyOutline

• inserts a horizontal rule before each top-level headline

• converts top-level headlines to all upper-case text

• numbers subordinate lines

• top-level headlines get <h3> tags

• second-level headlines get <h4> tags

sampleHomeRenderer

sampleScriptRenderer

siteOutliner

tableOutliner

twoLevelOutline

• very much like the fatHeadlines renderer

• top-level headlines are <h4>

• no indenting of headlines at any level

davenetoutline

Slides

• Create a discussion group message, then click the Edit With Radio button to open the document in Radio UserLand.

• Enter an outline that specifies your set of slides. Each top-level headline is a separate page, a separate slide.

• Choose Save from the File menu to save the outline to your Manila site.

rendered page

• rendered page looks very much like the outline in Frontier

-----

Rules about rules

You can include a <rules> section anywhere you like. It applies relative to the level at which it is included.

Each <rules> section contains one or more <rule>s. Each rule can have an optional "level" and/or "to" attribute that defines the scope of the rule. If the level attribute is not specified, it defaults to 1. If the to attribute is not specified it defaults to infinity (ie the rule applies to all subordinate text).

Each <rule> can have as many value tags as you like, chosen from this set: textStyle, textColor, textSize, textFace, outlineSpacing, leftIndent, labeling and internalLink. They are explained in the next section.

Legal rules

textStyle

If the value contains "bold" the text is displayed in boldface; if the value contains "italic", the text is displayed in italic.

textColor

Possible values: Any string that makes sense as the color attribute of an HTML <font> tag.

textSize

Possible values: smallest, smaller, medium, larger, largest.

For each of these, except medium, we generate a font tag, with size set to "-2", "-1" or "+1" or "+2"

textFace

Generate a font tag with the indicated text face.

outlineSpacing

Possible values: 1, 1.5 or 2.

Adds either 1, 2, or 3 <br> tags after each headline.

leftIndent

The number of pixels to indent for each level.

labeling

MORE has a labeling feature: you could choose between Leader characters, Harvard, Numeric, Legal, Bullets, and None. Numeric has been implemeted here, so far.

internalLink

Each headline renderered under this rule gets a left-arrow to the right of its headline, which is a name tag pointing to the permanent link for the headline.

The value of the element is the URL for the page in the archives.

Discuss

[Macro error: Can’t call the script because the name “commentIt” hasn’t been defined.] [Macro error: Can’t call the script because the name “commentIt” hasn’t been defined.]