> Wait a second do you use wicket:id tags in the 
>so when i see this:
> 
> public Object getObject( final Component c )
>            {
>                if ( ContentPage.this.isLocaleJapan 
> ese() )
>                    return "styles/main_jp.css";
>                else
>                    return "styles/main_en.css";
>            }
> 
> then you have to append the context path youreself. 
> 

Ok, now I know. And that does work, indeed.


>  <img src="/images/menu.gif"/>
> 
> Then you have to do it yourself!
> We don't touch urls generated by developer code.

Actually, I do this (relative URL):

  <img src="images/menu.gif">

Ok, so you are saying that I would have to create a wicket component for
ANY image or whatever I want to include?

So, this means that my authors, who know nothing about programming,
can't include images unless they can get a programmer to include a
component?

If I use a relative URL, why doesn't wicket prepend the context root? 

Is there a reason for this design decision? I trust the developers'
design decisions, but I don't understand this one. I'm just curious as
to why.


Cheers,
Dave





-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to