Re components:
check out the component reference in the wicket-examples project. it is farily complete and shows components in isolation so you can play around with them.
Re hibernate integration:
check out the wicket-phonebook project from wicket-stuff cvs. it is a simple example of a wicket/spring/hibernate project. wicket-phonebook has great javadoc that will explain what everything is.
Re creating components:
this is the strength of wicket. you just extend one of the base classes such as Component or WebMarkupContainer or extend any other component and away you go. checkout the code that drives components in the component reference its so simple it speaks for itself.
Re documentation:
yes this is something we do not have a lot of, we are working on it. what we do have right now is great javadoc. i got started just by looking at the examples and the code that drives them. wicket felt so natural i just picked it up ( but i did come from a strong tapestry background ). imho the best way to evaluate a framwork is to try and build a small project with it so you get the feel for it.
this list is a great place to get support.
if you have any questions feel free to email them to the list.
btw, wicket-examples and wicket-phonebook both have jetty-launcher in a class called Start, so if you use eclise just right click and do debug as java app, that will start up jetty and you are ready to go as opposed to package/redeploy cycle.
-Igor
On 11/16/05, Sam Gendler <[EMAIL PROTECTED]> wrote:
OK, so I've been all over the wicket sourceforge site, and I must be
missing something. Where is the documentation? There are some fairly
basic examples that don't go into much detail, the new user guide in
the wiki which is incomplete whenever it gets interesting. The wicket
stuff section lists a hibernate tool, but doesn't provide a link to
anything. I see many references to how great wicket is with hibernate,
but I've never seen a doc that describes how someone would actually
use wicket with hibernate. Perhaps most importantly, I've never found
a simple description of the components that are available (or how to
implement new ones), let alone how to use them. Do I really have to
extract all of this from the javadocs and source code?
I'm trying to evaluate frameworks for a large development project, and
from all the hype, wicket seems to be a nice solution, but it is
basically not evaluatable, since, apparently, the only way to learn
anything about it is to get deep enough into a development project to
overcome the learning curve and total lack of documentation.
Am I missing something here?
-------------------------------------------------------
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&opclick
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
