cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kimbro Staken <>
Subject Re: [provocative] crushing userland
Date Mon, 18 Feb 2002 10:50:49 GMT

On Monday, February 18, 2002, at 02:23 AM, Ugo Cei wrote:
> Done.
> I gave a quick look at Radio in the weekend and seen that it is based on 
> OPML ( I don't really like OPML though. Do you think 
> that we should use or support OPML, or use some other kind of markup?

Radio isn't really based on OPML, it's more based on plaintext. If you 
looked at the native app then everything is a really funky outline thing, 
that isn't really what Radio is to the user. Look at the web interface and 
the files generated through that. The native app just  sits in the 
background and controls everything. If you want to modify the code behind 
Radio, or access the object database directly, that's when you dig into 
the Radio app itself.

Radio uses a combination of the file system and its object database to 
store content. Most things go into the file system, but actual weblog post 
contents are stored in the object database as text. All typical end user 
interaction is through a web browser. When you post a new weblog entry it 
generates several static web pages and an RSS file and automatically 
uploads them to one or more servers.

The system does a lot of processing of the posted text, like turning 
things it thinks are URLs into links, email address into mailto links and 
automatically wrapping paragraphs in <p> tags. It has keyword expansion 
that can lead to unexpected and annoying results sometimes, especially 
since it isn't clearly documented. It also has macro capabilities that you 
can type directly into your posts. All of this stuff is used to generate a 
static web page, the published site isn't dynamic at all.

The system also monitors a directory hierarchy on disk so that any file 
you drop into it will automatically get published to the server. Dropping 
a .txt file will result it in it being turned into a web page with all 
your styles applied automatically. It applies the same processing there as 
it does for weblog posts. You can have different styles for different 
parts of the tree and can have them publish to different servers.

Style and publishing controls are done through text files in the file 
system. Any file that begins with a # is a Radio system file and won't be 
published to the server. Dropping the same file deeper in a hierarchy will 
override all like named files higher in the hierarchy.

Anyway, that's a quick overview. Overall, Radio is kind of weird, very 
quirky and has more then its share of bugs and annoyances, but I still 
find myself liking it more each day I use it. It feels dirty to say that, 
but it is what it is.

> 	Ugo
> -- Ugo Cei - Consorzio di Bioingegneria e Informatica Medica
> P.le Volontari del Sangue, 2 - 27100 Pavia - Italy
> Phone: +39.0382.525100 - E-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, email:
Kimbro Staken
XML Database Software, Consulting and Writing

To unsubscribe, e-mail:
For additional commands, email:

View raw message