Re: [PROPOSAL] Keel look and feel (Attn: Pierre)

Pierre

>
> I tested this css with IE 6 and FireFox without problem.
>
> The CSS menu is not the "absolute" way. But as a first step it's
> simpler than the javascript code in app-navigate. And if a more
> powerfull tool is needed then there is MenuStruts, JsCookMenu...
> It's also possible to keep the two and give a choice to the
> programmer. This is what I done in my project throughTiles definitions.
>
After much looking, I settled on the style.tigris.org methodology, as
Aleks suggested, and as I found out, Lou had already used in
app-scheduler.  One of the ideas there is to move everything to
CSS....which is what I am attempting to do.

I integrated your CSS-based menu into app-personality.   Works fine in
Firefox.  Also works in IE-6, but to a point. Looks like the location of
the  .htc file  is relative to the  HTML/JSP file that links to the CSS
file.  So, if you have the .css, .htc and .jsp in the same directory,
everything works fine.  Otherwise, we are out of luck.

Can you please see if you can make it work with the following structure:

http:/localhost:8080/mywebcontext/
   !--personality/style/css/style.css
   |--personality/scripts/csshover.htc
   |--dir1/test1.jsp
   |--test2.jsp

test1.jsp and test2.jsp both link to style.css. I can have style.css
define "body{behavior:url(../personalityscripts/csshover.htc);} to make
it work for test1.jsp.  Or,
"body{behavior:url(personality/scripts/csshover.htc);} to make it work
for test2.jsp.  But, can't get it defined to work for both.  It will
work OK if I define as
"body{behavior:url(/mywebcontext/personality/scripts/csshover.htc);},
but that means hard-coding the context name, which will not work for others.

Any ideas?

Shash