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
Jonathan Locke wrote:
the thing i love about this is that designers would not have to think
about links. they could just leverage dreamweavers extensive linking
functionality directly.
-------------------------------------------------------
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
