/You/ could contribute this as well! Use the wiki for this. If you can't access the wiki, email me a MD5 hash of your required password, and the username you want to use, and I'll add you to the wiki.
As it stands, the wiki could be used more. By contributing your findings, you help us in several ways: - you lighten the burden of our development efforts - you make (very explicitly) clear what kind of documentation you need - you help the community by sharing your knowlegde Your remarks are useful and the lack of good user documentation is troublesome. We are in the process of writing articles to help solve this. The main problem here is time and willpower. I'm a developer and I like writing Java most. I do see the need of a user manual, and am willing to go a long way but *procrastinating* just feels sooo gooood ;-) Martijn Jonathan Carlson wrote: >In my previous e-mail I mentioned having an index to example cdapp >source classes for how to do complex things. I'm sorry if I'm beating >on this too hard, but when I think something is probably important I >tend to beat on it. > >I look at Wicket kind of like I look at Lego kits. > >When I was growing up the Lego kits pretty much just came with a few >basic shapes and a couple of pictures on the box of a house or >skyscraper. That was cool, but it was all pretty basic and got boring >after a while. > >But now the new Lego designer kits come with many more shapes and sizes >and, more importantly, a 30-paged book giving step-by-step examples on >making complex air-planes, rockets, semi-trailer trucks, etc using the >same 150+ pieces in a kit. > >Suddenly Legos have become much more fun and interesting. Taking the >time to add an instruction booklet brings the full power of Legos and >the imagination of it's original designers to people (like me :-) who >don't have a lot of time or imagination to figure out how "standard" >pieces can fit together in different ways to create unique solutions to >complex problems. > >Sorry if I'm beating a dead horse. :-) I just liked the Lego analogy >and had to share it because I think it is relevant. I don't think >Wicket needs lots of step-by-step examples yet (although in a book >someday that would be great) but simple web pointers to possible >solutions in the example cdapp source code would go a looong way towards >the same end, IMHO. > >:-) > >- Jonathan > > >********************************************************************** >This email and any files transmitted with it are confidential and >intended solely for the use of the individual or entity to whom they >are addressed. If you have received this email in error please notify >the system manager. > >www.katun.com >********************************************************************** > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >_______________________________________________ >Wicket-user mailing list >Wicket-user@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/wicket-user > > > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
