|
I didn't have a look one the wicket books for quite while. Good you told
us. I orderered yours yesterday on Amazon. :) 2011/11/18 Igor Vaynberg <[hidden email]> > * there are three books written about wicket: two for beginners and > one for intermediate-advanced users. > * there is a searchable mailing list archive that spans years upon > years of users asking questions and getting answers. > * there is a wiki that lists examples and has some good articles. > * there is stack overflow questions and answers. > > is there an answer to every single possible question out there? of > course not. no framework has that. look at projects like spring and > hibernate. do those have great documentation? i bet you would say > "yes". are their mailing lists any less busy than our own? no. so what > does that say? > > if i had to make up a number i would say that armed with the resources > i listed you would be able to answer about 80% of your own questions. > and i think that is a pretty good number. there is a very active user > list to help you answer questions you cant answer yourself, usually > faster then a commercial support contract. for free. > > not too shabby. > > -igor > > On Thu, Nov 17, 2011 at 3:30 PM, Gaetan Zoritchak > <[hidden email]> wrote: > > I must admit that I agree with you. While I think Wicket is a > > great framework, the documentation is not up to par. This tool seems a > > little too elitist. "If you're strong enough you will find > > a great framework." It's a shame because even if the mailing list is very > > effective it slows down the adoption of wicket. > > > > 2011/11/17 geraldkw <[hidden email]> > > > >> "This is not an april fool's day, it is just an opinion of an > inexperienced > >> developer. " > >> > >> This illustrates one of the traditional logical fallacies. If you can't > >> effectively attack the argument, attack the speaker. > >> > >> My biggest problem with Wicket is that I haven't found any > documentation on > >> the web that really lets me get a solid grasp on the key concepts. I > read a > >> lot of poorly written "documentation", weak examples and forum posts > >> dealing > >> with something that is only vaguely related to my goals, maybe learn a > >> fragment of useful info, and then suffer while trying to apply it. > >> > >> I haven't looked a Wicket in Action or other Wicket Books, but I have > not > >> heard good things. Also, this is the Internet Age and this is web > >> programming. I have no problem finding documentation on other web > >> programming languages/frameworks like I do with Wicket. > >> > >> If I am wrong, point me to some solid learning materials, and you stand > a > >> chance of changing my mind. > >> > >> geraldkw > >> > >> > >> -- > >> View this message in context: > >> > http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-is-a-Flawed-Framework-tp4080411p4081206.html > >> Sent from the Users forum mailing list archive at Nabble.com. > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [hidden email] > >> For additional commands, e-mail: [hidden email] > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > > |
|
In reply to this post by robmcguinness
Super cool list, thanks a lot.
2011/11/18 robert.mcguinness <[hidden email]> > i'm baffled when people say the documentation is poor, the javadocs are > excellent and like igor said there are some great books (blogs too!). > books > and blogs get outdated fast since technlogy is rapidly advancing, so *use > the source luke!*. Not only will you learn Wicket, but I guarantee your > Java skills will improve. > > > awesome examples: > > > > https://github.com/apache/wicket https://github.com/apache/wicket (scan > over the unit test, best way to learn any framework not just wicket) > > https://github.com/55minutes/fiftyfive-wicket > https://github.com/55minutes/fiftyfive-wicket (fantastic) > > https://github.com/42Lines https://github.com/42Lines > > https://github.com/wicketstuff/core https://github.com/wicketstuff/core (a > gem, tons of examples on how to pretty much do anything) > > http://code.google.com/p/wiquery/source/checkout > http://code.google.com/p/wiquery/source/checkout > > https://github.com/jolira/wicket-stateless > https://github.com/jolira/wicket-stateless (wicket stateless is > excellent, > even easier with wicket 1.5) > > https://github.com/reaktor/oegyscroll > https://github.com/reaktor/oegyscroll > (endless pagination) > > http://code.google.com/p/wiquery/source/browse/core > http://code.google.com/p/wiquery/source/browse/core (jquery) > > http://code.google.com/p/jqwicket/source/browse/ > http://code.google.com/p/jqwicket/source/browse/ (jquery, learn from the > code and roll your own if it doesn't fit your needs, super easy > > https://github.com/rjnichols/visural-wicket > https://github.com/rjnichols/visural-wicket (great ui tools) > > https://xaloon.googlecode.com/svn/ https://xaloon.googlecode.com/svn/ > (excellent!) > > > > rob > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-is-a-Flawed-Framework-tp4080411p4082034.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > > |
| Powered by Nabble | Edit this page |
