I'm another that looks for documentation and examples when investigating new things. I'm not saying we need a formal/paper book (although they have their uses - my most recent purchase was a paper copy of Matt Raible's "Spring Live",) but I want something with at least a "Table of Contents" and a progression from beginning to an end (or at least a stage where a basic but usable web-app has been described).
I'm obviously keen on Wiki's, but would put an on-line manual higher as I want a tutorial to take me through various aspects, and the step-by-step approach tends ensures that there's no slight-of-hand going on anywhere, where there's too big a jump from one example to another. One of the the reasons I went for Dokuwiki was that it should lend itself to developing a manual/tutorial in the Wiki, though! Gwyn On 4/14/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hello, > > Never say never, rember that quote? > > Well Gilli, I may be in a minority of one but I do use manuals and books. > They are very important to me. I learn a lot from > them. > However, before talking about books let's create a great Tutorial about > wicket and develop more examples (agreed). > I think the original tutorial released by Jonathan was great and we should > revise and improve it. > Acticles, even just one pagers posted by the core team would be greatly > appreciated. Sometimes just an explanation of an > idea that was or is going to be introduced into Wicket is great. That helps > in understanding of a new code introduced into > Wicket. > But above all, now that wicket is beginning to be checked out by more people > small tutorials are a must. > Les > > ---------------- > Gilli wrote: > > On 14 Apr 2005, at 16:38, Gili wrote: > > I've read this quote a lot in the past and I think now is a good time > to repeat it: "Users don't read manuals!" We want > them, but never really read them. I know this is true for me... I read the > online Wicket manual cover to cover back when it > was up-to-date and in retrospect I would have much preferred a solid Wiki > knowledge base. > > My 2 cents is: instead of a online manual which people read from > cover to cover (no one really wants that anyway) > provide users with two things: > > 1) Wicket-examples (but more of them) > 2) Wiki knowledge base, i.e. "how to do this in Wicket..." > > A formal book is only needed if you want to sell it offline as a form > of making money or something but it is utterly > useless online. > > ------------------------------------------------------- > 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-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- 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_ide95&alloc_id396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
