- 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 proposeYes this is how it should work. Because then the pages doe work standalone (in dreamweaver)
the new one will ONLY work with admin/Home.html ("." => "/")
- /admin/Home.html could solve the absolute Path problem. But I
propose to combine it with a rootPackage name configureable through
AppSettings. Like rootPath=wicket.myApp and href="/admin/Home.html"
leads to class name wicket.myApp.admin.Home
And that is always my main goal. (at least i think in dreamweaver you can set a root dir?)
- May I suggest we make [autolink] depreciated first instead of
removing it as both approaches don't seem to contradict
- do you already have an idea on how to implement it? I guess it'll be
on Page level, right? I guess it'll have a cache to map found hrefs
with classnames. Stop: can not only be class name, what about images?
Are we going to treat *.html differently from everything else?
I see one big problem I have a Home.html in the root of the webapp and a Home component This should be documented that this can't be done.
Johan
------------------------------------------------------- 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
