To Do

To Do http://WellFormedWeb.org/news/11 This is my To Do list for RESTLog. Warning: incoherent ramblings on half-baked ideas ahead. Enhancements to add to the RESTLog client and server implementations, in roughly their order of priority: <dl> <dt><del>Template Editing</del></dt> <dd>Add the ability to edit the HTML and RSS template files. Should be able to GET them up in the edit box in RESTLogClient and then PUT them back. Requires adding to the RESTLog interface, probably add the URL <code>RESTLog.cgi/template</code> and then use content negotiation to refer to either the HTML or RSS template file. This will also require adding two more buttons to the client UI; "Edit HTML Template" and "Edit RSS Template" which when pressed all the other buttons need to disappear and replace the "Edit XXXX Template" to "Update XXXX Template". Have to also remember to disable the "Title" control. Update: <a href="http://wellformedweb.org/news/12">Completed</a>. </dd> <dt><del>Template Editing II</del></dt> <dd>Add handling to the client and server for the structured 'templates' format as it is outlined in <a href="http://wellformedweb.org/news/15">Template And Archive Revisions</a>. Update: <a href="http://wellformedweb.org/news/16">Completed</a>. </dd> <dt><del>Python Cleanup</del></dt> <dd>Make all the code in RESTLog.cgi into a library make RESTLog.cgi a simple called of the libraries. This will make it easier to upgrade when running RESTLog on multiple directories, for example here with one running the root and also in stories. Add the following line to the .htaccess file: <code>SetEnv PYTHONPATH /my/home/dir/lib/python</code>. In the process of cleaning up also ensure that all customization is done in RESTLog.cgi and confirm that installs in different directories can use a common set of template files if they want to. Update: <a href="http://wellformedweb.org/news/14">Completed</a>. </dd> <dt><del>C# Cleanup</del></dt> <dd>The RESTLog interface code needs to be cleaned up. Create a single HTTP class that has the following members: PUT(), GET(), POST() and DELETE(). For example: <code>HTTP.PUT(string URL, string ContentType)</code>. Update: Completed, just need to release the code. </dd> <dt><del>Archives</del></dt> <dd>Content will soon start rolling off the main page. Need to setup an archiving mechanism. The first brush idea is to provide a URI driven mechanism, such as: <code>RESTLog.cgi/1-20</code> which returns a page with items one through twenty displayed. Then I could provide an archive page <code>RESTLog.cgi/archives</code> that was dynamically generated with links to groups of postings in groups of twenty. This may tie into the searching. Update: <a href="http://wellformedweb.org/news/16">Completed</a>. </dd> <dt><del>Archives II</del></dt> <dd>Add handling to the client and server for the structured 'archives' format as it is outlined in <a href="http://wellformedweb.org/news/15">Template And Archive Revisions</a>. Update: <a href="http://wellformedweb.org/news/16">Completed</a>. </dd> <dt>_type=xml</dt> <dd>Using the simple extension ?xml is convenient but will cause grief for implementing search, need to add a second method of ?_type=xml. Support both styles. </dd> <dt>Excerpts</dt> <dd>Possibly add support for excerpts. Put the excerpts in the 'description' element and the full content in 'content:encoded'. Maybe. </dd> <dt>Search</dt> <dd>Need the ability to search the site using the URL <code>RESTLog.cgi?q=search+terms</code>. One thing to remember is that the search may have to operate on multiple data directories if you want to search across a site with multiple installs of RESTLog, like is done here with the news and a separate directory for stories. </dd> <dt><del>Cool URIs Don't Change</del></dt> <dd>Tweak the Python scripts and .htaccess files so that we conform as closely as possible to the suggestions in <a href="http://www.w3.org/Provider/Style/URI.html">Cool URIs Don't Change</a>. Update: <a href="http://WellFormedWeb.org/news/24">Completed</a>. </dd> <dt>Tidy</dt> <dd>Incorporate HTML validation into the client, possibly by shelling out to Tidy. </dd> </dl> BitWorking, Inc