Jesus. Time spended at this endless talk read and write could be spent in writing one simple Demo app. Simple demo app reqest is very legitimate. And my vote is for demo app without Ant, Maven also. Demo App just based supposed basic knowledge of Servlet technologies, or just be familiar with WAR directory layout. Wicket is realy very simple so it would be good if this simplicity would be underscored also by demo app. Maven has its good points and also weak ones. But generaly it is used mostly on company levels and not on the levles of individial newbies. Most of them just know hov to write servlet, JSP and so on. and this I think major part of framework newbies needs to understand strength of wicket. Maven ads some virtual complication to the proces that not many newbies know maven and when seen first time they can be scared of it. So they can back off. IMHO one needs to firstly understand basic concepts, based just on very simple premises like beeign familiar with WAR and t hen this concept could be widened by using maven and point out some benefits of it. Maven + Wicket for firstimers can be simple too much and can leed to presumption that Wicket must be used with Maven. IMHO More didactic way maybe should be. 1. Needed prereq of WAR file layout 2. setup Wicket demo app on this knowledge. 3. Descriv\\be what is behind curtain of wicket app on one simple wicket tag decorator. 4. describe how to enhance using Maven. Wicket is framework which is fast learnable and I beleave when getting the point you can write application within just one hour. More didactic aproach to demo could lead to greater adoption
As soon as I finish my work of testing some frameworks, this could be within two weeks I can write some demo app with simple explanation taking more didactic aproach :-) just let me know to whom I can send it, and the format of the wiki. Confrontation at this thread is just useless ... Robo ----- Originálna Správa ----- Od: chickabee Komu: Poslaná: 08.09.2007 15:06 Predmet: Re: First Day Disgust! > > 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] > > __________ BLOG - Váš denník umiestnený na internete, v ktorom môžete sprostredkúvať svoje myšlienky, zážitky a nové informácie - http://blog.sme.sk/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
