Totally agree. I like to understand what is going on so I created a 'sandbox' type project in Netbeans, manually referenced the wicket libraries, created the application and webpage class with related HTML, and the Web.xml. I was up and running in under an hour. The application runs on Tomcat with iBatis and mySQL - nothing fancy no Jetty, Hibernate.
My process of learning the framework is again simple. Add pages to the 'sandbox ' application and add components to the page that I want to learn/play with. Before I knew it I had working examples of most of the Wicket components with Java code I had written and understood. I like Wicket. I have the greatest respect for the developers who devote their time to giving us a worthwhile framework, and to the Wicket community who are always willing to help. My advice is to build an application manually, the information is on the Wiki and in many blogs (just Google it). Read the book 'Pro-Wicket' and sign up to the Manning MEAPs version of 'Wicket In Action' Ryan Holmes wrote: > > Funny, one of the things I remember being really impressed with when > I set up my first Wicket (1.2) app was how incredibly easy it was: > > 1.) Add wicket jars > 2.) Write "hello world" home page > 3.) Write WebApplication subclass and specify home page > 4.) Map servlet in web.xml > 5.) Hit "run" button in Eclipse w/WTP (or whatever your tools of > choice are) > > I figured all that out from this obscure page on the wiki: http:// > cwiki.apache.org/WICKET/newuserguide.html#Newuserguide- > MyFirstApplication > > Of course, most people would never guess that a page entitled "My > First Application" in the New User Guide might hold the information a > new user would need when writing their first Wicket application, so > perhaps Wicket is only intended for really, really smart people. > > -Ryan > > On Sep 8, 2007, at 6:06 AM, chickabee wrote: > >> >> Thanks for providing me the primer on web applications and Ant and >> for not >> trying to understand what point I am trying to make here. >> >> Yes, we are not dealing with nuclear science here and Yes again >> wicket is >> just another web application, Did someone disagree with that. I >> hope not. >> >> Once you are out in the market to try the new webapps then it >> always makes >> sense to have people be able to get up and running on the basics w/ >> o efforts >> and not to have to deal with tricks necessary to get basic app to >> work. >> >> A common expectation is a simple standalone app without >> Maven/Spring/Hibernate etc unnecessary stuff. Run 'ant' on the >> command line >> and here u have the war file, now, make a few changes to >> experiment and >> then run 'ant' again to have modified war. Simple. >> >> Obviously the current example is for the comfort of wicket creators >> and not >> for the comfort of prospective users and that is the problem here. >> >> Any one with basic common sense will get this up and running after >> a day's >> tinkering around, but that can be avoided by adding simple things >> here in >> the examples, that is the point I am trying to sell here only if >> there are >> buyers out there with open mind. >> >> >> ======================================== >> >> Al Maw wrote: >>> >>> chickabee wrote: >>>> Thanks for the great idea. >>> >>> Note that this is displayed fairly prominently on the web site at >>> http://wicket.apache.org under "QuickStart". >>> >>>> It believe it will be good to put a few of the examples >>>> application in >>>> their own folders and war files so that they can be studied >>>> independently >>>> without the clutter of 20 projects. >>> >>> We used to have this, however, grouping all the examples into one >>> project has several big advantages: >>> >>> - Getting all the examples running in your IDE is much easier. >>> - We don't have ten extra projects to manage the build files for. >>> - We can easily link to all the examples from a single page. >>> >>>> Another thing I notice is that maven is the default build tool >>>> used for >>>> wicket, I guess it will be good to provide the ant build.xml, >>>> just in >>>> case >>>> someone does not want full maven features. >>> >>> I think we need to write a page on this on the web site that we >>> can send >>> people to. ;-) >>> >>> An Ant build for Wicket isn't special. If you don't know how to >>> use Ant, >>> it's not our job to show you. There are no magic custom Ant tasks we >>> provide, or JSP pre-compilation steps, or anything like that. All you >>> need is to compile your app with the necessary dependencies, just >>> like >>> any other Java app. You'll also need your web.xml, etc. just like any >>> other Java web app. Nothing special here. >>> >>> Regards, >>> >>> Al >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >> >> -- >> View this message in context: http://www.nabble.com/First-Day- >> Disgust%21-tf4405663.html#a12569457 >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/First-Day-Disgust%21-tf4405663.html#a12584665 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
