So we are going to test every <a href> to see if it points to a wicket page (you try to get a page constructor for the given href i take)
If this doesn't take to much resources (memory and cpu) then this looks good to me.
johan
Gili wrote:
Jon and I would like to propose a replacement for autolinks. Instead of users explicitly declaring [autolink], we'd automatically convert <a href> tags to autolinks and treat their query string as page parameters. This new approach is capable of replacing all preexisting autolink functionality.
PRO:
- Automatic conversion of internal links to autolinks (as opposed to having to explicitly declare them). - We no longer run the risk of broken links resulting from developers forgeting to link <a href> tags with Wicket pages.
CON:
- Overhead of resolving the <a href> tags the first time the Page is ever rendered. We need to resolve URLs to Wicket pages dynamically, and cache them for future rendering.
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
