Hacking Radio by Charles Miller
Tales of my hackery with Radio Userland, and useful links thereof.

 







Click to see the XML version of this web page.

Click here to send an email to the editor of this weblog.

 

 

  Tuesday, 5 February 2002


Oh, and I forgot to say a public "Thanks Dave" for giving me a script to see what was in the Page Table. I think that script's going to be useful for quite a few things as I poke around in the future.
10:21:29 PM    

Roland Tanglao read my Hacking Radio piece, and told me that I could buy the O'Reilly book on Frontier, but it's out of print.

Believe it or not, that book's been sitting on the remainder shelf in the Dymocks shop in the middle of Sydney for months. It's half-price, even. I almost bought it today (on the way to getting the NIN and Muse CDs), but I read in the book that it was written for an old version of Frontier, and that even when the book was coming out, they anticipated substantial changes that would make the book obselete. Is this true, or should I rush off and buy it tomorrow?


10:17:05 PM    

Dave Winer responded to my Radio problems. [Scripting News] I guess that means I now have a Dave Number of 1.

Yes, Radio needs better documentation. If it's any help, the only language I ever managed to learn purely from the product homepage was PHP. It's well organised, very easy to navigate, and the open commenting feature on each page means that the community fills in the gaps over time, as well as adding tips, caveats and useful patterns.

I get the feeling that UserTalk is a lot like PHP - a simple language where the power lies in the library of available functions (and in Radio's case, the integration with the Object Database). The difference with Radio is that it's putting this power on the desktop rather than server.

I also get the feeling that Manila, while good for blogs, doesn't really have any mature templates when it comes to organising information non-chronologically. Its search function is bad enough that it makes it harder to find information (if it was absent, I'd have used google to start with), its directory template is almost painful to use, and it doesn't seem to organise meaningful relations between pages very well.

A weblog, and discussion groups/bulletin boards are accretions of knowledge. You read them day by day, and you absorb information as you go. Occasionally, you'll need to find something that happened a week ago, and you go back through the calendar. Very rarely, you'll think "Yeah, that was mentioned last year", and you'll need a search function. Other than that, the information put on a blog fades with time, and rarely organises itself along any other lines.

Compare this to, say, Wiki, where following information chronologically is impossible, directories are almost always only one level deep, but the site self-organises on the way pages (information) relate to each other.

Anyway, I've digressed.

Memo to self: write story about how Radio's price-tag makes it more likely to need good documentation than a $10,000 program, but least likely to get it than Open Source.


10:09:33 PM    

I tried to start programming in Radio today. I didn't get particularly far, basically because it was so difficult to find out how any of it worked: Hacking Radio Part 1: DocSpotting
3:14:37 PM    



Click here to visit the Radio UserLand website. © Copyright 2002 Charles Miller.
Last update: 7/2/02; 12:25:22 PM.

February 2002
Sun Mon Tue Wed Thu Fri Sat
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28    
Jan   Mar