http://cwiki.apache.org/WICKET/framework-documentation.html
On 8/9/07, Alexander Schatten <[EMAIL PROTECTED]> wrote: > I completly agree; just one addition: best-practices are completly > missing in the introduction. at least a list what is available!! > > how should I know, that there is apparently an authentication framework? > how do I access DAOs properly? there is support for working with > databases (is there?) > > there is apparently a validation framework. I cam so far to understand > (by browsing javadocs and a lot of trial and error, as again, > documentation is not coherent, wiki, javadoc) that I can add validation > rules to form elements, like this field should be min 5 max 10 chars and > the like. ok, I have it running so far, that no other entries are > excepted in this field, but I have no idea how I can react within the > application for wrong entries, missing entries (you would want to give > the user feedback that an entry was wrong). so where is the hook? > > how is the lifecycle of objects? where do I hook in to do special > things? always in the constructor? somewhere else...? (there was a > similar posting on this list recently) > > these are just examples: accidentally you stumble over a feature, that > you were just on implementing yourself, and then it takes hours or days > to figure out how to use it properly. > > again: extremly frustrating. > > > > Johan Maasing wrote: > > I have been playing with wicket for the last week. I must agree with > > what Alexander says. The documentation is rather lacking and quite > > frustrating. To bad because wicket is cool. So +1 for better docs. > > As a newbie to wicket I can't help in writing it but I can tell you > > what I find frustrating: > > > > The javadocs is not linked from the wicket site, it was hard to find > > even using google. > > > > The component reference is not complete. The examples have a link to > > 'view source' but it does not say which files to look at for a given > > example. It would be helpful if the component reference said which > > component belonged in which jar-file (wicket or wicket-extension). > > Personally I think that tapestrys component reference is helpful > > (http://tapestry.apache.org/tapestry4.1/components/index.html) > > Perhaps there could evolve some kind of javadoc convention or other > > documentation-convention for components that describes the component, > > the parameters, the css-classes the component renders and so on. > > Oh yeah, the component reference app is stateful so I constantly get > > session expired when looking at the examples, I can't for the life of > > me figure out why :-) > > > > It was a bit hard to find a reference to the wicket-tags, at least it > > is linked from wiki, but a schema-file would be helpful to get command > > completion in the HTML-editor. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Wicket joins the Apache Software Foundation as Apache Wicket Apache Wicket 1.3.0-beta2 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
