Hi, Slightly off topic, but this is the summer vacation season on this hemisphere, so I'm sure no one will mind:
On 8/16/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > Wicket assumes that UI designers are *designers* (and not > half-programmers like ZK assumes) only dealing with laying out, and > that UI logic can best be coded in Java (by programmers obviously). 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. Gabor Szokoli --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
