"Gustaf, XoTcl code might be faster but so far its incredibly difficult for most OpenACS developers to read. Processors are cheap and programmers are expensive. As I said before, having consisten code is a goal, but so far there hasn't been any effort to produce any sort of documentation on how to USE XoTcl wisely within the OpenACS framework. Unfortunately, until that happens you'll end up doing all the work yourself."
I would concur with this. I've been using XOWiki for the last couple of weeks as it looks like a perfect fit for an upcoming project but I find it hard work to figure out whats going on. I'm not new to OO (don't get me started on J2EE!) and I've read the tutorial on XOTcl http://media.wu-wien.ac.at/doc/tutorial.html and worked through the code but I'm still struggling to figure out how some of it works.
I appreciate the time Gustaf has spent on this and I can see the advantages that he talks about. I think it could be very productive but its not going to be taken up for other packages and projects simply because we can't work out how to do it.
Perhaps what we need is an "XOTcl in OpenACS" tutorial along the lines of the XOTcl Tutorial.
