yes thats what normally happens, see the ImageTest for example, the
last locale en_US has no image for that locale so we don't generate
it. Thats because normally the packageresource knows to which locale
it resolves to and the resourcereference is getting that locale when
it loads the resource in
Ok, please give me some time, i will ask someone (who is reading) with
Netbeans 6 already installed to help me produce a quickstart.
Anyway, i insist that now is all working for me, just that it is strange
that it generates the HTML referencing the CSS with full locale and style,
and then when
when wicket generates the links it appends your browser's locale to them
so the link to foo.css will look like foo_en_us.css for example.
then when the url is requested wicket does the resolution with fallback:
first try foo_en_us.css
then try foo_en.css
then try foo.css
so it all still
So perhaps there's nothing wrong after all?
It seems that Igor Vaynberg wrote:
when wicket generates the links it appends your browser's locale to them
so the link to foo.css will look like foo_en_us.css for example.
then when the url is requested wicket does the resolution with fallback:
the only thing that is wrong is that perhaps we COULD generate a url
without locale and we DONT. but i am american, so im not that familiar
with the whole locale thing. johan is a better guy to ask for this...
-gor
On Nov 10, 2007 1:24 PM, German Morales [EMAIL PROTECTED] wrote:
So perhaps
no problem.
:-)
f(t)
ps: even from my cel, on a date, saturday night, sad... :-)
On 11/10/07, German Morales [EMAIL PROTECTED] wrote:
Ok, please give me some time, i will ask someone (who is reading) with
Netbeans 6 already installed to help me produce a quickstart.
Anyway, i insist that now
Hi,
I was thinking (as a last hope) that if this works for the HTMLs, i could
provide different HTMLs that point internally to different CSSs, and it
should work. But that would be duplicating the HTML just to have the CSS
changed, and then it's not a good idea.
Perhaps someone can tell me an
if you are creating your own ResourceReferences then you have to give the
style and locale to them
We could enhance the constructors that it does Session.get().getLocale() and
Session.get().getStyle()
if you dont give them..
johan
On Nov 9, 2007 10:27 AM, German Morales [EMAIL PROTECTED]
it should fallback just fine..
what version of wicket are you using?
Because in the ResourceStreamLocator we do now this:
public IResourceStream locate(final Class clazz, String path, final String
style,
final Locale locale, final String extension)
{
// Try the various combinations of
Hi,
Well, i'm not sure to want to be creating the ResourceReferences on my
own. Is there another way to have the same i have for HTML (automatic look
up by the framework for localized and styled versions) but for CSSs?
German
It seems that Johan Compagner wrote:
if you are creating your own
version 1.3.0-beta4.
I insist that the problem must be something different, perhaps in the way
i pretend it to work. I know about the ResourceStreamLocator, and as i
tell it works perfectly for the HTML. The difference is that from my class
the framework looks automatically for the corresponding
no as i said before
you have to create the resourcereference with the locale and the style.
Those are not automatically picked up from the session. If you don't give
them in the constructor
then both are just null
What you could do is this:
ResourceReference reference = new
Hi again,
With your solution, the generated HTML now looks this way:
link rel=stylesheet type=text/css
href=resources/path.to.mypage.MyPage/style_mystyle_mylocale.css /
i don't have style_mystyle_mylocale.css, but only style_mystyle.css
But it works!
So it seems that wicket later (when the
But even with bind() it still shows you the locale in the url?
On Nov 9, 2007 3:22 PM, German Morales [EMAIL PROTECTED] wrote:
Hi again,
With your solution, the generated HTML now looks this way:
link rel=stylesheet type=text/css
Furthermore, now that i understand more about this, i tried again my
original version:
cResponse.getHeaderResponse().renderCSSReference(new
ResourceReference(MyPage.class, style.css, getLocale(), getStyle()));
and it also works as expected.
Perhaps i was not expecting it to work because the
Yes, at least that's what i see when i ask Firefox to show me the source
of the page.
It seems that Johan Compagner wrote:
But even with bind() it still shows you the locale in the url?
On Nov 9, 2007 3:22 PM, German Morales [EMAIL PROTECTED]
wrote:
Hi again,
With your solution, the
I think i asked this before, but what version of wicket??
Normally (in the current wicket 1.3 buids) a ResourceReference to a
PackageResource will fallback to the real locale the PackageResource is
loaded
from after the ResourceReference is binded.
johan
On Nov 9, 2007 3:34 PM, German Morales
1.3.0 beta 4
It seems that Johan Compagner wrote:
I think i asked this before, but what version of wicket??
Normally (in the current wicket 1.3 buids) a ResourceReference to a
PackageResource will fallback to the real locale the PackageResource is
loaded
from after the ResourceReference is
they locale and style are used to search for it yes
they are not forced.. What do you mean with that?
If the file with that style and locale isn't there it will fallback
johan
On Nov 7, 2007 10:50 PM, German Morales [EMAIL PROTECTED] wrote:
Hi all,
I'm having trouble with localized and
Hi johan,
The problem is that the file is there... just that it doesn't seem to be
looking for it.
If i force the full constructor:
new ResourceReference(MyPage.class, style.css, getLocale(), getStyle())
all works, so the file is correcly found and the name is correct.
The problem is when i
Hi,
I use it inside a page.
I've tried...
// inside the page constructor
add(HeaderContributor.forCss(new ResourceReference(MyPage.class,
style.css)));
and
// inside renderHead
cResponse.getHeaderResponse().renderCSSReference(new
ResourceReference(MyPage.class, style.css));
And
21 matches
Mail list logo
