Andreas Aderhold wrote:
All those kept up-to-date should really do nice. I think good an well maintained docs are the key factors for wicket to prevail. I, as a user, value them more important than features. i don't have the time to read the source code or dozends of wikis or blog examples. i prefer a central well structured reference i can use. I also learned that it is way better starting docs in early phaseand postpone some features than having to write a huge doc later on.
I agree with you, but... not all programmers are good writers. I had a go at it, but I find it very hard to write a good guide. Furthermore, working on Wicket is also about scratching my itch. I (/ the company I work for) need better web frameworks for building our systems. And as I can't be working on it full-time (the company needs a good framework, but it is not it's core business to build one), I have to decide where to spend my time on. My time is best spend coding and participating in this list (which is also crucial for new people... maybe even more so than having a decent user's guide). Someone with a different skillset - a writer - should do the manual. I hope Geertjan will continue to help us out here...
Cheers, Eelco ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
