Falls sich jemand von Euch damit (oder mit dem Active Renderer) schon beschäftigt hat, bitte ich um Erfahrungsberichte The Live Outline Tool is the most direct way to edit a website ever. Think of it as a "public notepad" that's structured. One outline for a whole website. No saving required. Where it once took three steps to publish to a website (the Edit this Page concept) now it takes zero steps.

Use Live Outlines to keep people in your workgroup up to date on your progress as you take work notes in the Radio outliner.

Download and install 

Download LiveOutline.root.

Save it into the Tools sub-folder of the Radio UserLand folder. (Mac users set the file creator to LAND, type to TABL.)

How to get started 

Choose the Open Outline command from the LiveOutline sub-menu of the Tools menu. An outline window opens.

This outline is an entire website. Every top-level headline is a page.

Enter a headline. Then indent and type some text underneath it.

To see the top-level of your website -- to see a list of all the pages -- choose View Top Level in Browser in the LiveOutline sub-menu of the Tools menu. This presents a page that lists all the top-level headlines in your outline. Click on any link to view that page.

You can use rules to change the formatting of the outline -- the outline renderer is the same one you use when writing for Manila sites.

How to get the URL of a headline 

You can get the URL of any headline, not just top-level headlines, by selecting it and choosing Copy Headline URL from the Live Outline sub-menu.

This puts the URL on the clipboard. You can then paste it into another outline, an email, wherever you like.

How to edit the template 

Choose Edit Template to edit the template for your Live Outline site. You can make it look however you want. The default template is very plain -- there's plenty of room for creativity.

For people who've built websites in Frontier before, you'll note that behind the scenes is a simple Frontier website. If you want to lift the hood and add macros and so on, you can.

Next Mindbomb: Easy Images from the Desktop by Dave Winer

OK, this is really nutty -- but I have the Tool working, the one I talked about on Saturday on Scripting News, now it's time to clean it up for a beta release, and get a discussion going. If you're a developer and wondering how the Tool works, ask questions and I'll try to answer them. The art of tool-writing is coming along, and I'd like to see what questions people have.

Rules of Tools 

Tools are not like parts in Radio.root, where you have to be careful to only add or modify scripts in certain tables. You can change my Tool if you like. You can customize it to make it work the way you want it to. I've designed it in such a way that if you want to lift the hood, you'll see extra power that doesn't show up in the user interface. You can even distribute your changes, but if you do so, please change the name, so I can keep improving mine. This is something like open source. Make it easy for people to be generous. Apply the Golden Rule, do unto others as you would have them do unto you, and everyone will be happy and empowered.

How this Tool works 

There's a special folder called the Watched Folder -- you control where it is, but it defaults to your operating systems' idea of where pictures should be stored. We create a sub-folder of that folder called Radio Upstream. Any files you copy into that folder are consumed by the My Pictures tool. If it's a picture it copies it to the destination folder, which defaults to the images sub-folder of your Radio www folder. So you don't have to worry about this tool messing with pictures that weren't intended for it.

How to Install 

First Update Radio.root. Without this it can't work.

Then download myPictures.root and save it into the Tools sub-folder of the Radio UserLand folder.

After about a minute, Radio will see it's there, and open it and install it. (If for some reason it doesn't install, quit and restart the Radio app.)

Configuring the My Pictures Tool 

The first thing to do is to enable the tool and tell it where you want it to look for pictures, and where you want them stored in your www folder. To do so, go to the desktop website home page, scan down the right edge of the screen looking for the link to My Pictures, note that it is currently disabled, and click on the link to get to the configuration screen.

Check the box to enable the tool. Verify that you like the folders that it chose. Think about the template, you probably don't want to change it now, but you never know, you might want to later.

Here's a screen shot of the configuration page.

How to try it out 

For my tests I've been using the fantastic Zeldman icons. I open a folder containing all the icons and drag a few into the watched folder. The My Pictures tool has a thread running in the background, and when it sees picture files, GIFs and JPEGs (sorry no PNGs yet) it copies them where they will (probably) get upstreamed. It checks every five seconds.

The Tool installs an upstream callback so it knows when the file is publicly visible, and it knows its URL. Then it generates the <img> tag it needs to make the picture show up in your Web page. When you're finished copying files into the folder, the home page of your desktop website will open, you might have refresh it. Voila, there's the HTML code for all the images (if you're using the wizzy editor, you'll see the images themselves, click on the Source radio button to see the source, if you want to).

How to get new versions 

This tool has a lightweight update mechanism that's pretty easy.

If you see me talking about a new feature and you want the latest version, here's what you do.

1. Bring the Radio app to the front.

2. From the Tools menu, choose Refresh Code from the My Pictures sub-menu.

3. Confirm that you want to get the latest code.

4. Proceed with your life.

Note: In case this doesn't work -- try downloading a new copy of the tool to your Tools folder. You have to quit Radio first, because the Tool database will be busy. Sorry for the glitches. Programming in the fast lane.

Multi-Author Weblog Tool by Jake Savin

 A multi-authored weblog has posts that appear on the home page which are written by a group of people, instead of by a single author. The Multi-Author Weblog Tool makes it easy to use Radio to create a multi-authored weblog.

Examples of multi-authored weblogs are Meme Pool and Boing Boing.

How to Install 

1. Download multiAuthorWeblog.root and save it into the Tools sub-folder of the Radio UserLand folder.

2. From the home page of the desktop website, look in the right margin, scroll down if necessary, and click the Multi-Author Weblog link. This will open the Tool's configuration page.

3. If you don't see the Multi-Author Weblog link on the destktop website home page, quit and restart the Radio application.

How to configure 

After completing the steps above, you should see a page with a table of feeds you're subscribed to, and a pop-up menu at the top for choosing a category to route to. Next you'll need to tell Radio which feeds to route. Here's how:

1. First, make sure that you're subscribed to the RSS feeds of all of your authors. You can either subscribe to their feeds directly using the subscriptions page, or you can click the XML Coffee Mug on their sites.

2. Return to the Tool's configuration page.

3. Use the pop-up menu at the top of the page to choose a category to route posts to, or you can choose the Home Page to route posts to your main weblog.

4. In the table of subscribed feeds below the pop-up menu, check the box to the left of each of your author's feeds.

5. Scroll to the bottom of the page, and click the Submit button.

The next time the news aggregator scans for new items, any new posts in your authors' feeds will automatically be posted to the category you picked.

How it works 

Everyone in the group writes with their own copy of Radio and publishes their weblog in both HTML and RSS. One of the editors takes responsibility for running the Multi-Author Weblog Tool, which joins all the individual feeds into a single weblog. This person is the webmaster of the multi-authored weblog.

Each hour when the news aggregator scans for new posts, any new items appearing in your author's feeds are automatically posted to the webmaster's weblog.

If you're the webmaster, it's important that you leave Radio running with the news aggregator enabled, at least during the hours when your authors will be writing new posts, since Radio can only update the weblog when the news aggregator scans for new items.

Technical details 

This section explains how the Tool works from a technical standpoint. It's for developers and the technically curious, so don't worry -- you don't have to understand this stuff in order to use the Tool.

The Multi-Author Weblog Tool hooks in to the news aggregator's callbacks. When a story arrives, and if it's in one of the source feeds, it's posted to the designated category (or to the home page).

There are three callbacks: a preScanCallback which creates a temporary table in which newly arrived posts are stored, a storyArrivedCallback which stores the posts in the table, and a postScanCallback which posts any new items to the weblog.

All of the code is in the multiAuthorWeblogSuite table, inside multiAuthorWeblog.root.

How to include author names in a Multi-Author Weblog

Tue, Jul 23, 2002; by Lawrence Lee.

If you are running a weblog using the Multi-Author Weblog tool, you can include the title of the RSS channel in your weblog by adding the following macro to your Item Template for the weblog.

<%local (adrpost = @weblogData.posts.["<%paddedItemNum%>"]); if defined (adrpost^.sourceName) {return (adrpost^.sourceName)} else %>

Note: the RSS feeds for all the authors need to use their name as the title of the channel.

See also 

Multi-Author Weblog Tool

Liebe Betablogger oder gibt es schon ein paar Alphablogger unter Euch???....ich poste jetzt ein paar von den Dokus zu den tools mit denen ich bisher herumgespielt habe.

to distribute notifications about new orders via an RSS feed (together with the regular e-mail messages). It didn't take much to implement with the IdeaTools framework (rss feeds are rendered trough our xsl system). There are a couple of things to consider about this solution:

• The feed has to be password protected, but the only authentication that aggregators can manage is basic authentication, with username and password included in the feed's url. It's relatively simple to do with Frontier or any other web server;
• A nice thing I found out about the Aggregator in Radio is that it does not include password protected feeds in the mySubscriptions.opml public file (thanks UL);
• What we are doing at this level is just plain notification, meaning that we're just publishing some basic data about the order to be rendered in the aggregator, the next step is going to be defining a namespace for the orders and using this feed to interface to the accounting system.

[Paolo Valdemarin: Paolo's Weblog] [thomas n. burg | randgänge]

Blog a from in transition?. From .blog to converged client..

[...]

Blogging is a form in transition.

Personally, I think blogging as a form will merge with all the other forms of digital expression. With email and IM first. With voice/video conferencing, streaming videos, browsing, and PowerPointing later.

Watch it change:

• as more people blog from their foto-mobiles
• as devices start to blog ("My car's day")
• as audiobloggers create radio shows and videobloggers create televsion programming
• as Sims characters start to blog.

Moving forward, see a convergent software client emerge.

Source: evanwolf group, 2002.

[mehr] [a klog apart klogging] [Phil Wolff: community]

[thomas n. burg | randgänge]

Simon Willison's Weblog. Mir scheint es wichtig den Report von Rick Klau nochmals mit diesem Fazit zu zitieren, ich denke die Potential werden damit erneut und nachhaltig sichtbar.

Rick Klau: A K-Log Pilot Recap: Given the flexible nature of weblogs (unlike structured applications, weblogs really can be what you want them to be), it wasn't entirely surprising to see users shape their own expectations in testing out the software:

• A senior developer saw Radio as a great annotated bookmark tool - a way to save URLs and provide his own commentary for others in his team.
• A marketing manager saw Radio mostly as a clipping service - the ability to snag snippets from other web sites to save to her own site.
• A sales person used Radio to distribute industry news relevant to other sales people.
• A QA tester who frequently lunches with customers in training often provided recaps of discussions at lunch - sharing the customers' interests and inquiries.

[thomas n. burg | randgänge]