Another good idea would be to have some graphic clue about hyperlinks in the new wiki CSS.
On 8/22/05, Gregg D Bolinger <[EMAIL PROTECTED]> wrote: > Oh, another point: > > > > Where do resources go? (HTML files, css, etc) - It was easy enough to find > out after I downloaded the examples and extraced the WAR file. Seems > simpler to just say "put HTML files in the same package as associated class > files. Gregg > > > On 8/22/05, Gregg D Bolinger <[EMAIL PROTECTED]> wrote: > > I ran across David Heffelfinger's newest tutorial on Wicket and decided to > give it another look. I liked the tutorial and I have contacted David > regarding it. While I was going through the tutorial, there were some > things that David left out which I had to go to the Wicket homepage to find > out. Unfortunately, this proved painful. If these suggested documentation > notes are already on the wiki I apologize. I went through the new users > guide and these things still seem to be missing. > > > > > > > > Definition of a home page - It seems that the definition of a home page is > missing. What would seem correct is that the applicationClassName defined > in the web.xml fits this bill. However, I can find no mention of this > anywhere. > > URL to run "Your first application". Ok, this may seem obvious to some > but for me it wasn't and still isn't for the most part. What url do we use > to start the applications? And where is information about how that is > determined? > > Form classes as subclass as WebPage - Is this a) good OO design and b) > required? What are the advantages/disadvantages to keeping Form classes in > their very own class? > > PropertyModel/CompoundPropertyModel - These things seem > confusing to a new user. More so I feel for users coming from a framework > like Struts or Webwork. I was able to understand it a bit better coming > from a Tapestry and JSF background, but the documentation on this could use > some work. It seems there is really just enough to confuse people on how to > use them. > > These were the major things that stood out and could be fixed very quickly > I feel. I also feel that as a newbie to Wicket these are problems that most > newbies will run across. I like the looks of Wicket and I think it's a step > in the right direction for webapp development. I love the NO-XML policy. > Keep up the good work and please don't take this as a complaint. Mearly a > suggestion. > > > > Gregg Bolinger > > > > > > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
