I wrote a script for use in the Markdown.root tool. It’s purpose is to check and see if a tool is loaded given the name of the tool as a parameter. [Steve][1] says that I should just use [`user.tools`][2] but I think doing what I did is easier. If I used `user.tools.databases` I’d have to…

Read More

[**Steve Kirks**](http://houseofwarwick.com/) says: >[**Donovan Watts: Radio’s Librarian**](http://houseofwarwick.com/2005/02/23.html#a1212) >After watching the many outstanding entries at Donovan’s Radio: The Missing Manual, UserLand made him and offer he couldn’t refuse: Radio’s Librarian > >Welcome aboard, Donovan–and thank you! Congratulations Donovan.

Read More

I made a bunch of silly changes tonight to the Markdown.root. Silly because they weren’t necessarily needed. Most have to do with changing what `MarkdownSuite.utils.getPrefs` returns. It now returns the complete path to the prefs table so `adrPrefs^ = [toolName]Data.user.prefs.[toolName]` instead of `[toolName]Data.user.prefs` . Many scripts to change for that. I updated the version number…

Read More

I’ve made a number of changes to the way the Markdown tool interacts with [activeRenderer][aR]. Firstly, nothing has changed in the way that Markdown interacts and renders the weblog. The only changes were in how the Markdown tool deals with OPML files. There are 3 different ways of interacting with OPML files in activeRenderer. These…

Read More

Thanks [Donovan][1]. This has a bit of markup in it. [1]: http://becomethemedia.org/radio/

Read More

As [Marc][1] had originally written, the user prefs were stored inside a new table in `weblogData.prefs`. For a number of reasons, including forward compatibility we had decided to change this so that the prefs are now stored in a new table at `MarkdownData.prefs.user.Markdown`. The default prefs are still at `MarkdownData.docs.prefs`. So far there is no…

Read More