A lot of tbd :) I think if you want to compare, there's nothing that beats taking a look at code. Wicket has e.g. a hangman example and a component reference (part of wicket-examples); if you take a look at that code, and maybe try something yourself, you should get a fairly good idea.
Some of the main differences: * Wicket is not a managed framework. That means that you - the programmer - are in charge of component creation yourself. You do this with javacode opposed to doing it declarative. Pro: gives you flexibility/ you wont be limited by what the framework builders thought up/ you don't have to learn how the framework manages and how the declaring language (xml) works. Con: harder to integrate with other frameworks somethimes/ wicket internals sometimes difficult. * (like Igor said) Wicket purposefuly does not support scripting like features in your markup. Pro: everything stays very clean and it is easier to guess how things should be done. Con: harder for people that are used to a 'php/jsp way of doing things' and you need programmers that at least understand the basics of OO Java programming. Pro: clarity and cleaneness. Con: some things are more work with Wicket and you have to keep your java component tree in sync with the markup nesting. * With Wicket every component is truly stateful. Every property you define is part of it's state, and there is a flexible undo mechanism you can use to support any advanced backbutton support you might want. No need for a rewind mechanism. Furthermore, wicket component can be nested and can take part of any collaboration you want in the same fashion you could do in e.g. Swing. Pro: flexibility and very easy to do complex things if you know your Java. Con: sometimes easy to end up with unoptimized spaghetti like code if you take too many short cuts (much like you could have with Swing). * Creating custom components with Wicket is super easy. Just extend from an existing one (or from base class WebComponent or WebMarkupContainer), make it available in your classpath and your done. There's no extra configuration (libraries) and magical strings (ids) involved. For advanced component initialization, you can use IInitializer. Hope this helps, Eelco On 11/17/05, Marco van de Haar <[EMAIL PROTECTED]> wrote: > I don't really know if it's up to date, but you could check > http://www.wicket-wiki.org.uk/wiki/index.php/For_Tapestry_Users > > in the Wicket wiki > > Marco > > Detlef Schulze wrote: > > > Sorry, should read: "tapestry and wicket or wicket and WebObjects" of > > course ... > > > > -----Original Message----- > > *From:* Detlef Schulze > > *Sent:* Donnerstag, 17. November 2005 12:59 > > *To:* [email protected] > > *Subject:* [Wicket-user] Wicket for tapestry users > > > > Hi, > > > > the last projects I was involved I implemented with tapestry. > > > > I am of the opinion that it is important (and interesting) to > > check once in a while what the "competitors" are doing ;-) > > > > So the question is: Is anybody aware of some online resources > > where tapestry and wicket or tapestry and WebObjects are compared? > > > > > > cheers, > > detlef > > > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. Get Certified Today > Register for a JBoss Training Course. Free Certification Exam > for All Training Attendees Through End of 2005. For more info visit: > http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28&alloc_id845&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
