2009/10/16 Gavin <ga...@16degrees.com.au>: > > >> -----Original Message----- >> From: Ross Gardler [mailto:ross.gard...@googlemail.com] >> Sent: Friday, 9 October 2009 5:08 AM >> To: dev@forrest.apache.org >> Cc: dev@forrest.apache.org >> Subject: Re: [Important] Status and future direction >> >> I agree with Tim here, especially the bit where he can't agree with me >> more ;-) >> >> I don't know a great deal about Cocoon 3, but I have no personal >> interest in using it here - sledgehammer to crack a nut. Since I'm not >> active here my opinion doesn't count for much in that respect though. >> >> If someone wanted to look at and validate my evening hacks on Forrest >> 2 I might be drawn back in, I do have a need for such a lightweight >> and embeddable solution. However, I don't have the time or resources >> to drive forward alone on this. > > I seem to be in the same camp as Ross and Tim. When it comes to the Cocoon > side of things, even after all this time it is a maze [/haze] to me. > > I would like to take a look at Forrest2 more before deciding if that could > be a possible future or not. A couple of questions on Forrest2 > > How usable is it right now?
It isn't usable at all. I merely hacked together a very rough prototype to illustrate what I was talking about. It works in a very small number of test cases that are designed to demonstrate rather than implement. > Does it depend on our current core in any way or can the Forrest2 directory > tree be moved away and still work independently? It is fully independent. > How far off do you think it is in terms of the tools that our current > Forrest offers? (can you drop an odt file in from our current plugin system > and get a tei output for example) See above - it is a long way off. This is *not* the right route if people are not fully supportive of the idea. Ross
