Thomas Mäder wrote:
>
> Wicket is a framework to write (mostly) statefulweb pages. Unlike other
> web
> frameworks it does not impose a particular way to structure the
> application
> logic beyond that. Think of it like, say, the QT widget set. It's a way to
> display information and to be notified of user interactions.
>
> Thomas
>
> PS: when did the notion start that design pattens had an intrinsic value?
> "Now new and improved with more patterns!" Patterns are ways to structure
> code WHEN IT NEEDS STRUCTURING. A HelloWorld app DOES NOT NEED PATTERNS.
> (sorry for the shouting, pet peeve)
>
>
I hear you Thomas. Maybe I should ask the question another way...does
anyone out there encapsulate their data access layer/service layer within
their model or do people put that stuff in their pages/components? Is anyone
using any patterns? if not...i feel so last year!
--
View this message in context:
http://www.nabble.com/patterns-for-web-ui-apps.--mvc-models-tp18214140p18231819.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]
