> We've been using wicket for a couple of months now, our first > application is about to be deployed, so I looked back at the templates > and started wondering how much this separation of concerns applies to > us. > We have a base page with some panels supplied by subclasses, then > those panels are made up of subpanels, fragments, datatables, all with > their respective HTML templates. We have a wrapper panel for each form > input component to add a label and a nicer read-only view. All this > even before we introduced a navigation border! > > We did start from a single HTML page from a designer, and all we had > to do was slice that up, so there is some truth to the separation of > concerns, but it is was a one-way road, there's no way the designer > will understand all these HTML sniplets: We can only ask him to > beautify a full, rendered page, and slice that up again to update the > small template files. > > I'm not complaining or anything, haven't used any other web framework, > and still can't see any I'd switch to, (well, theoretically, if > designers could do OpenLaszlo all by themselves and we only had to > supply the business logic via a web service...) just wanted to share > my thoughts on the separation of concerns slogan.
I agree: especially if you break your application up in many panels, it can be hard to keep an overview. So sometimes, there is something to say for following a more page based approach in favor of reusability. However, part of the argument still holds as even broken up in panels, you still don't have to deal with loops, conditionals, etc in your markup. It should still pretty much be a 1-1 translation, where the only extra thing you do is break it up in smaller pieces. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
