Mikhail Fedotov wrote:
> 
> Hi!
> 
> > This once again clearly shows that Cocoon needs marketing
> > !
> 
> Good point, but I've been trying to do some basic stuff in
> cocoon for the last few days. I was able to do all
> information I want, but at least half of that information
> come from java sources. I've been had to use full-text
> search in local copy of cvs!
> 
> That's not documentation; while core concepts are clear (at
> least, I understand them), smaller parts are almost
> non-documented. Even matchers could be used as en example:
> I've been had to check out sample application to understand
> how wildcard session parameter matcher works, and don't yet
> understand how request parameter matcher works.
> 
> If we don't want to frighten people right after they came
> to play with c2 their first time, those things must be
> documented. I.e. there should be centralized and unified
> documentation list for all components like matchers or
> database actions. Almost noone will look in sources
> comparing to the whole crowd of potential users.
> 
> So, docs first, then (optionally) write current plans and
> components in development, including scratchpad, and then
> it will be perfect time for marketing.
> 
> The best thing is that both parts (I don't count marketing)
> are very simple. Requred docs can be no more verbose than
> javadocs, i.e. context of use, parameters, short (and maybe
> long) description and examples.
> 
> ps. I could try to work on it if I'll pass my current
> exams.

We are perfectly aware of the issues with documentation and we are
moving as fast as we can to improve things, believe me, also along with
the forrest effort.

I'm pretty sure that things will be better in time and the fact that
more and more articles come up is a pretty good sign of it anyway.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<[EMAIL PROTECTED]>                             Friedrich Nietzsche
--------------------------------------------------------------------



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to