Dave Bauer said: > I am surpised that you though development speed was reduced. I find that > the greatest asset of OpenACS. It is a complex system, and there is > definitely a learning curve though. Once you understand it, I guess it is fine. The reason there is a steep learning curve is because it is designed to be used with the default user interfaces (.tcl files), which you edit (or use templates) to make OpenACS look like you want it. _that_ is easy. Creating a custom homepage or a new module that uses authentication and permissions is horrible because the documentation just is not there. (http://openacs.org/api-doc/package-view?version_id=5)
I don't see what is so hard about describing all your procedure in a way similar to Javadocs. It's a catch 22 situation for the developers; developers don't like doing docs, but they want as many people as possible to use it. Personaly, I would prefer a package that does not have and client-facing pages at all, only admin pages and a good API documentation. Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
