i'm not sure i agree that the performance impact matters. and the current method is arguable at least as error prone. also, you omitted the advantage of transparency. the transparency of links just working the way a designer would expect is pretty huge.
i think i'm still 0 (undecided) on this and think that we need to kick it around for a bit longer until we all feel like we're on the same page (hopefully)...
Eelco Hillenius wrote:
I made up my mind about the autolink replacement proposal (which is that instead of using <a id="wicket-[autolink], all anchors would be scanned and tested for matches with Wicket pages).
I am -1 on this. I see one theoretic advantage (not having to think about adding the [autolink] id) and many disadvantages (less clarity, performance impact, error prone... see discussion).
Regards,
Eelco
------------------------------------------------------- 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
