<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>Advogato blog for tdxdave</title>
    <link>http://www.advogato.org/person/tdxdave/</link>
    <description>Advogato blog for tdxdave</description>
    <language>en-us</language>
    <generator>mod_virgule</generator>
    <pubDate>Sun, 26 May 2013 09:35:11 GMT</pubDate>
    <item>
      <pubDate>Thu, 27 Jun 2002 18:38:48 GMT</pubDate>
      <title>27 Jun 2002</title>
      <link>http://www.advogato.org/person/tdxdave/diary.html?start=6</link>
      <guid>http://www.advogato.org/person/tdxdave/diary.html?start=6</guid>
      <description>Building a web-base content management system is hard. The work isn't necessarily hard, but he decisions are. Mainly, should or should I not include this kitchen sink. There are basically two main classes of CMS that I have seen. Super flexbile, powerful, incomprehensible systems, or simple easy to use systems with few features.

&lt;p&gt; Working on OpenACS 4.5, I was introduced to a new application for OpenACS called edit-this-page. It's goal is a simple, easy to use, and easy to extend CMS. I am working on the next version, and the temptation to add more and more features that would "be nice to have" is very strong. Deciding what is necessary, and what is optional is very tricky. It is also probably impossible. It is better to build a good base that can be extended. OpenACS is a toolkit to build applications. It is a given that there will be code written to customize it. I think this is the way to go. Leave methods to extend and add features available, but do not build in too much.
</description>
    </item>
    <item>
      <pubDate>Fri, 24 May 2002 14:49:00 GMT</pubDate>
      <title>24 May 2002</title>
      <link>http://www.advogato.org/person/tdxdave/diary.html?start=5</link>
      <guid>http://www.advogato.org/person/tdxdave/diary.html?start=5</guid>
      <description>Well forget NSSoap. It looks like development has stopped on
it, and I can't seem to get it to work. I am forging ahead
with TclSOAP http://tclsoap.sourceforge.net as the base. I
have mainly run into problems with loading standard Tcl
packages into AOLserver. We are working on getting the
package require command, and Tcl namespaces working, and
changing the way Tcl interpreters are created inside AOLserver. </description>
    </item>
    <item>
      <pubDate>Tue, 27 Nov 2001 14:13:01 GMT</pubDate>
      <title>27 Nov 2001</title>
      <link>http://www.advogato.org/person/tdxdave/diary.html?start=4</link>
      <guid>http://www.advogato.org/person/tdxdave/diary.html?start=4</guid>
      <description>I have pretty much stopped working on nsxmlrpc because of 
&lt;a href="http://nssoap.sf.net" &gt;NSSoap&lt;/a&gt;. NSSoap is based 
on TclSOAP which has XML-RPC support built in. So I can get 
SOAP and XML-RPC in one package.</description>
    </item>
    <item>
      <pubDate>Tue, 28 Aug 2001 16:26:38 GMT</pubDate>
      <title>28 Aug 2001</title>
      <link>http://www.advogato.org/person/tdxdave/diary.html?start=3</link>
      <guid>http://www.advogato.org/person/tdxdave/diary.html?start=3</guid>
      <description>ns_xmlrpc is ready to go as a generic AOLserver add-on. I 
fixed it so that it creates any procs it needs that are not 
already defined. It should be available as a tarball very 
soon.</description>
    </item>
    <item>
      <pubDate>Wed, 15 Aug 2001 16:25:50 GMT</pubDate>
      <title>15 Aug 2001</title>
      <link>http://www.advogato.org/person/tdxdave/diary.html?start=2</link>
      <guid>http://www.advogato.org/person/tdxdave/diary.html?start=2</guid>
      <description>I got the &lt;a href="http://usefulinc.com/chump/" &gt;Daily 
Chump&lt;/a&gt; IRC bot running on the #openacs 
channel on irc.openprojects.net. It is a weblog created by 
logging all the URLs typed into the channel. It's written 
in Python so I really have no idea how it works. It creates 
XML files and comes with XSLT stylesheets to transform it 
into HTML.

&lt;p&gt; Anyway the cool part is that I used the new version of &lt;a href="http://acs-misc.sourceforge.net" &gt;ns_xml&lt;/a&gt; to run 
through all the XML files and convert them to HTML as an 
AOLserver scheduled proc. Check it out at &lt;a href="http://www.thedesignexperience.org/openacs/ircblog/" &gt;h
ttp://www.thedesignexperience.org/openacs/ircblog/&lt;/a&gt;.</description>
    </item>
    <item>
      <pubDate>Wed, 11 Jul 2001 15:44:25 GMT</pubDate>
      <title>11 Jul 2001</title>
      <link>http://www.advogato.org/person/tdxdave/diary.html?start=1</link>
      <guid>http://www.advogato.org/person/tdxdave/diary.html?start=1</guid>
      <description>Works is starting on turning ns_xmlrpc into a real live 
OpenACS module. When we are done OpenACS 4 modules will be 
able to call and provide XML-RPC services.</description>
    </item>
    <item>
      <pubDate>Wed, 23 May 2001 19:58:33 GMT</pubDate>
      <title>23 May 2001</title>
      <link>http://www.advogato.org/person/tdxdave/diary.html?start=0</link>
      <guid>http://www.advogato.org/person/tdxdave/diary.html?start=0</guid>
      <description>My main weblog is at my homepage. I use XML-RPC with 
OpenACS to maintain it. Right now I am working on a small 
part of the OpenACS 4.x port. </description>
    </item>
  </channel>
</rss>
