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
Hmmm. I'm not convinced yet. I like it from a designer's perspective
(not having to use id=wicket-[autolink]), but really dislike it from a
programmers perspective (implicit behaviour is scary).
Gili wrote:
Jon and I would like to propose a replacement for autolinks.
Instead of users
And one more thing. Say, you've got Home.html relative to your current
package, and you've got Home.html in your webapp directory. Is see a
problem here.
Eelco
Eelco Hillenius wrote:
Hmmm. I'm not convinced yet. I like it from a designer's perspective
(not having to use id=wicket-[autolink]),
- How are we going to support absolute package-path?
we should.
- I recall Jon talking about an alias map (Admin.html =
administration/Home.html) to be set through AppSettings
not preferred by me.
- The currenlty implementation works with admin.Home.html. I propose
the new one will ONLY
I am still +1 for a change that allows autolinks to work with other
packages. Like 'admin/Home.html'.
Eelco
Juergen Donnerstag wrote:
Please be a bit more specific. The current [autolink] feature is
limited in that it is only able access subpackages (see javadoc
resolveAutolink) - kind of
am still +1 for a change that allows autolinks to work with other
packages. Like 'admin/Home.html'.
you mean / instead .? Because admin.Home.html is already
supported. Though I admit it doesn't look very nice.
Juergen
---
The SF.Net email is
Yep, that's what we mean :)
Juergen Donnerstag wrote:
am still +1 for a change that allows autolinks to work with other
packages. Like 'admin/Home.html'.
you mean / instead .? Because admin.Home.html is already
supported. Though I admit it doesn't look very nice.
Juergen
How are we going to support absolute package-path?
Users can specify the Webapp base path, like you suggested.
You certainly know this is a problem JSP world and the reason why
almost all frameworks have something like $contextPath variables.
Something, I definitly don't want.
On Thu, 30 Dec 2004 20:06:13 +0100, Juergen Donnerstag wrote:
How are we going to support absolute package-path?
Users can specify the Webapp base path, like you suggested.
You certainly know this is a problem JSP world and the reason why
almost all frameworks have something like
On Thu, 30 Dec 2004 23:23:57 +0100, Eelco Hillenius wrote:
Silly? Why is that? 'Unless you explicitly convert them'? The old
behaviour is to add a link a id=wcn-[autolink] etc. Why do I end up
with broken links? I add these links just as I add components like:
span id=wcn-blah
You end
10 matches
Mail list logo
