Hi All, I've done some work on xooki to be able to generate the documentation, to avoid packaging xooki in the distribution. This works pretty fine now, but I now realize we may have a legal issue. Indeed, the documentation rely on a small javascript for the menu found here: http://www.dynamicdrive.com/dynamicindex1/navigate1.htm
The problem is that even when the doc is generated we need to package those scripts if we want to have the same tree view as on the web site. But this script hasn't a standard OSI approved license, so I think it's a problem to distribute it, isn't it? If we really can't distribute it, we can remove it completely (in this case the menu will be always fully expanded) and I can review the menu generation in this case to generate only the relevant parts (what is opened by default when you navigate to the page). I'd prefer keeping the menu, especially if we later want to use the batch generation instead of in browser generation for the public website (to improve accessbility and web crawlers compatibility). Maybe I could make that an option during batch generation... WDYT? - Xavier
