Daniel Ferreira Castro wrote:
In lots of books about wicket I can see a Page implementation declaring a
Form as an inner class of the Page.
Of course that this is, in part, a personal preference.
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.
Is there any reccomendation that denies such thing?
It's probably a matter of preference and how big your form code actually is.
And also, regarding Forms yet...
If I declare a Form as a top class should I have a markup html for it
because this form will be treated as a component?
No, Form doesn't extend WebMarkupContainerWithAssociatedMarkup.
--
Leszek Gawron
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
