On Tue, 2002-07-09 at 10:40, Martijn Verver wrote: > 1) First steps > - What is MMbase and what is the structure of Mmbase > - How to create a content cloud. > - How to add a piece of content to the cloud > - How to create a new MMbase object type > - Using relations in a JSP page How far can we say that creation of tools can replace the documentation? When a tool can offer a much cleaner interface to MMBase, with the result that less documentations is needed.
> 2) Installation guide > How to install MMbase on the following application servers: > - Tomcat > - Orion > - WebSphere > - WebLogic > - Others? Does the installation differ that much on different application servers? Is this our fault? How will we solve this? > Using the following databases > - Oracle > - DB2 > - MySQL > - Progress > - Others? PostgreSQL The rights of all directories, used by MMBase... I think that this also makes it clear for the developers that we should work to create a MMBase, which is friendly in terms of behaviour towards a database, a application server and ofcourse the users and administrators. This way less documentation is needed, thus making the time spend on documentation more valueble. ps: i find the documentation project a very good thing, but i also want to make clear the MMBase should be simple.(and i think it can be much clearer) When something is simple, it's much easier to describe in documentation then something with a lot of different behaviours depending on the given situation. -- Eduard Witteveen Systeem Ontwikkelaar NOS Internet, Gateway C Kamer 107 +31(0)356772910 http://www.omroep.nl/ Sed quis custodiet ipsos custodes? : The sixth Satire from Juvenal
