I propose we change the search path of the jetspeed template locator
service to include browser directories. The changes will be made to the
current JetspeedTemplateLocatorService.
The search path algorithm would be the same as now, with the addition of
the browser directory if there is at least one defined browser group (see
below) and the getRequest().getHeader("USER-AGENT") matches one of the
browser group strings (ie starts with).
The most important question is were do the browser specific directories go
in the heirarchy. The problem we are trying to solve is that browsers
display content differently and might need custom templates. We also want
to avoid duplication and keep the search speedy. This would imply that the
browser specific directory should be at the highest level possible
(earlier/nearer top of the tree) and that if there are no browser groups
defined that the search for browser directory will not be included.
Here are some examples of what I propose:
case 1: All older browsers have a particular behavior, like no
javascript. The site is english but has localization enabled.
In JR.p:
services.TemplateLocator.browsergroup.sansjavascript="Netscape 4" "Netscape
3" "Internet Exploder 1"
in WEB-INF/:
templates/vm/layouts/html/en/default.vm
templates/vm/layouts/html/sansjavascript/en/default.vm
case 2: All netscape browsers have a particular bug. The site is english
and spanish.
In JR.p:
services.TemplateLocator.browsergroup.netscape47="Netscape/ 4.7" "<spanish
equiv if different>"
in WEB-INF:
templates/vm/layouts/html/en/default.vm
templates/vm/layouts/html/es/default.vm
templates/vm/layouts/html/netscape47/en/default.vm
templates/vm/layouts/html/netscape47/es/default.vm
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
