+1
Eelco
Jonathan Locke wrote:
i have an idea to resolve this which might work for everyone. we could introduce <wicket:link> for explicitly declaring autolinks ([] still goes away, thank goodness). then we could make an app setting setAutomaticLinking(boolean) to allow people to turn on the "implicit" behavior. the default would be off and docs would explain aliasing behavior of automaticLinking. it's a compromise, yes. if we can't agree on the availability of this feature, i suppose we should stick with current functionality alone (just <wicket:link>).
i think we need to continue to support the ability to include web pages, images and other resources on the classpath because we need to be able to jar up components with their whole resource set. i believe this worked last time i looked...
Eelco Hillenius wrote:
------------------------------------------------------- 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
