Ok, ok. You know what? I'll just back off from this discussion, and see
where it heads. Maybe, I'll be convinced along the way, but for now: 'me
-1 for automatic anchor processing'.
Eelco
Gili wrote:
On Sat, 01 Jan 2005 22:12:06 +0100, Eelco Hillenius wrote:
The thing I loath about this is that it is implicit. You have to explain
a designer that the anchors will be parsed and that, depending on what
Wicket pages there are, the anchor wil point to either a static resource
or a Wicket Page. The current situation is better as it is allways
immediately clear what it does.
Eelco,
But this is beyond the scope/concern of a web designer.
Personally I expect the designer to work on the presentation layer
while a programmer works on the Java layer. It is up to you, the
developer, to decide how to render the page (from a dynamic point of
view). It is up to him to provide you with the HTML file containing the
guiding design (static layout).
Gili
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
