Tuesday, October 25, 2005

Testing rendering of OPML files Created a projects folder within the devknowledgeorama folder and created index.opml as a test. Tried to use the radio.upstream.folderNeedsScan verb, but had some problems (did not see upstreaming). Tried another version of this verb (radio.upstream.folderNeedsUpstream), but still no luck. Finally, I added another colon at the end of the path to the folder, and that seems to have made it work. Downloaded the rules OPML file from Mark Woods' article on writing renderers in Radio UserLand. Typed some text in index.opml, saw the rendered results on the web site. Noticed that the title of the page is echoed in the main page text. Copied template.txt from devknowledgeorama folder, deleted the second of the following two lines: radio.macros.editorsOnlyMenu p class="title" title That eliminated the title from the main text. After that worked, I created a subfolder in projects called directorytool, and copied the template.txt and index.opml file from the projects folder. Edited the index.opml file, had to use radio.upstream.folderNeedsUpstream to get the folder to upload. I guess the folderNeedsScan will not work if the folder has not been upstreamed at least once. Did a test of the Directory Tool by deleting all of the directory files on the web server and running the tool. Saw the expectecd dialog boxes for each directory being rendered, but none of the files were uploaded. Used the radio.upstream.folderNeedsUpstream verb to move the rendered files to the web server. Will need to update the tool and documentation to handle this problem. 5:26:47 AM