Yep, and thank you for submitting those issues.
What I meant is that *someone* should work at the user's manual. That doesn't require deep API knowledge, but it does require good English writing skills. Juergen, Johan, Martijn (though he might give it a try sometime) and I fall in the category 'not English/ American/ Canadian natives'.
IMO, delivering a Wicket 1.0 without a good user's manual would be like delivering a house without a front door.
Eelco
Gili wrote:
Jon has already asked me. The problem is that I don't know enough about Wicket to be able to document it. If a method/class has no documentation I am basically clueless as to how it should work in the first place. The most I can do, from a newbie's point of view, is point out when the preexisting documentation is confusing and should be clarified. I have already filed specific bug reports against some documentation and suggested some alternative text.
Gili
On Mon, 03 Jan 2005 20:32:28 +0100, Eelco Hillenius wrote:
Gili, are you interested in documenting (user's manual)?
Eelco
Jonathan Locke wrote:
yeah, i understand that. i think good javadoc is asking enough of devs, especially with the language issue. i can't take on the docs, but will help with javadocs.
jon
Eelco Hillenius wrote:
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
