[AgileWiki] Cabinet ArkDbPropertiesAndTables is now complete, what's next

[Bill la F. <bil...@su...>]

Well, it looks like we've now got the basic documentation needed to 
understand the AgileWiki, though we could probably use something on 
descriptor units. And it also looks like the server is reasonably 
stable. Cheers!   :-)

At this point I want to switch back to writing a bit of code, specificly 
the remove parent command. And then get ready for the 3.0.0.0 release. 
My attention is also turning to what we need for 3.1. There are several 
possible directions:

1. AgileWiki 3.0 is not at all agile, to the point where I don't enjoy 
using it. At a minimum I think we need the post, promote and demote 
commands from AgileWiki2.

2. The table API needs to be made bi-directional. Its just a bit wierd 
the way it works now.

3. We need a better way to install applications than having to create a 
whole new Ark from scratch.

4. Every Rolon should have its own URL which can be referenced from 
external web pages.

To date, the focus has been on getting AW3 to the point where it can 
self-host its own documentation. But there are areas which are seriously 
broken. These need to be addressed.

Bill