David Crossley dijo:Are you saying that, in order to access the docs by doing cocoon servlet then http://localhost:8888/docs/ would access a local Forrest dist, rather than the Cocoon dist itself, but would use the local Cocoon? That could work. It would need a suitable "to see the docs, download Forrest" message.
David Crossley wrote:
Antonio Gallardo wrote:Perhaps we can solve this dilemma by avoiding it. We could
I noted almost all the docs in Cocoon website is in the "old"document v10 of Forrest:
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN""../dtd/document-v10.dtd">
Can we change to the "new" format v12?
Yes, but there is a problem. We could change all the docs to v1.2 and the generation of docs via 'build docs' should be okay.
However, remember that docs are also built via the webapp localhost:8888/docs/ and this still uses stylesheets that are specific to v1.0
http://wiki.cocoondev.org/Wiki.jsp?page=ForrestProposal
... this identifies some of the issues. The complexity is probably why
no-one has been brave enough to do this job yet.
remove the docs generation stuff from the webapp. If people
want to do live docs, then they could install Forrest and
'forrest run' on another port. We already ask them to install
Forrest if they want to 'build docs'.
+1
That way we will don't worry about the forrest version inside cocoon. And will can also remove it at all.
I am also aware about the upayavira comment. I think the idea is not to
remove the docs from Cocoon, just allow to generate using an external
forrest dist.
But you know what that would mean? I would actually, after all this time, actually have to download Forrest!
Regards, Upayavira
