Hi, I've been following up on the whole documentation discussion and I have a few ideas.
First of all, there is one thing all of us can do: Post on the users mailing list what were the hardest obstacles that we had to overcome in Wicket. (If everyone thinks that's a good idea, I can start such a thread). What was hardest to understand and what explaination was hard to find. With that kind of feedback in the back of our heads, it should be easier to write useful docs. Second of all, I think the Wicket Wiki would be a great place to start with a structured documentation. It would be easy to keep it up to date and it would be easy for everyone to participate. We could coordinate efforts on the mailing list. Of course a wiki can't replace a "static, official" documentation, but the stuff that gets written on the Wiki can easily serve as a basis for official docs. And one more thing: I think special cases or combinations of components that you need in real world applications would be very useful. And yes, I'd definitely would be willing to contribute, too :) - Johannes ------------------------------------------------------- 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
