It wouldn't be a "drawback," since nobody does it better.
But anyway, you can preview a component (in isolation) just fine in the component template without a web server. You can also preview the fake version in the page template without a server, though it's easy for that to get out of synch with the real thing.
Your designers have to understand where everything is, but I think the preview (or, you can use an HTML editor) claim holds up.
Nathan Eduardo Rocha wrote:
The fact that one cannot preview html only using panels without running a web server means that java code it is mandatory. Do you think this is a drawback to Wicket (as well as Tapestry) that claims that designers and coders can work almost independently?
------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
