So if I understand you correctly:
I can enable autolink application-wide with AppSettings but should I
wish to manipulate autolinks on a finer level I can use regions to
override that default. Correct?
It is possible for me to modify the application-wide default
(enabling autolinks) without inserting a single <wicket:link> to make
it work right?
Gili
On Wed, 19 Jan 2005 20:42:47 +0100, Juergen Donnerstag wrote:
>You may remember that not everybody liked the idea of having just an
>application level setting. I personnely think you'll need some means
>like [autolink] to change the default setting for specific tags. And I
>don't think that a page or component level setting is sufficient for
>the same reason. The most flexible approach and one which meets the
>autolink opponents and proponents is to have <wicket:link> regions.
>AppSettings will maintain the app default and by means of
><wicket:link> region, you may change that default. That region may be
>a single anchor tag or it could be the complete <body> of a page.
>
>Juergen
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
>Tool for open source databases. Create drag-&-drop reports. Save time
>by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
>Download a FREE copy at http://www.intelliview.com/go/osdn_nl
>_______________________________________________
>Wicket-develop mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/wicket-develop
>
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
