Daniel Ferreira Castro wrote: > > I think, in my opinion, that the approach of declaring the Form as an > inner > class makes the code more "dirty". I mean, the Page class grows a lot and > by inspecting the code is hard to understand at a first glance the scope > of > each entity and field. So I prefer to declare the Form as a top class > instead inner class. >
No. First of all, your page class should not keep growing larger and larger. You should put most of the logic into your domain classes, not in the page class. Once you do that, your page should be clean and easy to understand despite the presence of an anonymous Form subclass. Second, the structure of the Java code should match the structure of the HTML file. This will make it easier to understand how they work together. ----- -- Kent Tong Wicket tutorials freely available at http://www.agileskills2.org/EWDW Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA -- View this message in context: http://www.nabble.com/A-doubt-regarding-%22best-practices%22-tp21849426p21869946.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
