If you don't want to maintain HTML/CSS and also have that generated
look at the layout manager frameworks like Echo2

johan



On Nov 16, 2007 7:21 AM, Joe Toth <[EMAIL PROTECTED]> wrote:

> Compare the java code to something in velocity/jsp like...
>
> href="/path/to/something.jsp?id=${draft.id}"
>
> ...I know, I know...you really can't compare the 2 because wicket's
> version can have a lot more functionality easily. But, your ABSOLUTELY
> POSITIVELY right about paying with maintainability, except you still
> have to maintain the HTML file, yuck.
>
> 99.9% of the time I am very very happy with Wicket and wish that
> everyone used it. I hate working on JSP/JSF projects because "it's the
> standard and blah blah crap crap".
>
> I liked the last "Con" though. "Everything has to be done in Java" - I
> know what you meant, but its still funny. I wish everything could be
> done in Java, even the design. And I don't mean HTML+CSS, but some
> magically awesome design engine that would output HTML+CSS.
>
> With a Wicket application its A LOT easier to figure out where
> everything is and how it gets there. OO w00t. Ah, the days of PHP/JSP
> hell.
>
>
>
> On Thu, 2007-11-15 at 21:20 -0800, Eelco Hillenius wrote:
> > > Example would be a link on a table...
> > >
> > >
> > >                 columns.add(new LinkPropertyColumn(new
> Model("Delivery"), new Model(
> > >                                 "change")) {
> > >                         @Override
> > >                         public Link createLink(final Item item, String
> componentId,
> > >                                         final IModel model) {
> > >                                 return new Link(componentId) {
> > >                                         @Override
> > >                                         public void onClick() {
> > >                                                 ReportStatistic
> reportStatistic = (ReportStatistic) model
> > >
> .getObject();
> > >                                                 DraftProduct draft =
> productService
> > >
> .getDraftProduct(reportStatistic.getReportId());
> > >                                                 setResponsePage(new
> ReportDelivery(draft));
> > >                                         }
> > >                                 };
> > >                         }
> > >                 });
> > >
> >
> > For the record, this code fragment doesn't look like 'too much Java'
> > to me tbh. The decision to load the draft and redirect to another page
> > could be done in Velocity, but would immediately mean that you pay
> > with maintainability.
> >
> > Eelco
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to