Some 1.4 code:
getPageSettings.setAutomaticMultiWindowSupport(false);
now can't compile in 1.5.
Does this mean Multi Window Support is always on and can't be turned off
in 1.5?
I guess I could just not bother creating any ResourceReference instance
and simply use:
renderCSSReference(externalUrl + "pbModalWindow.css");
>-Original Message-
>From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
>Sent: Sunday, 18 September 2011 8:34 AM
>To: users@wicket.apache.o
The table in the Wiki suggests replacing
1.4 ResourceReference
With
1..5 PackageResourceReference
But what if the 1.4 ResourceReference was not a package reference but
specified by a URL?
Eg.,
ResourceReference CSS = new ResourceReference(externalUrl +
"pbModalWindow.css");
Your
a bunch of people sitting in a bar chatting and drinking beer... :)
-igor
On Fri, Sep 16, 2011 at 4:44 PM, Nelson Segura wrote:
> Can you explain how does it work? I am thinking on going to java one
> just to check this out.
> -nelson
>
> -
Hi Duy,
which wicket, inmethod-grid versions are you using?
Regards,
Attila
2011/9/17 Duy Do
> Hi Wicketers,
>
> I have a problem with inmethod-grid in IE8 as below error. This issue
> cause the grid display incorrectly. Is it a bug? And how to fix it?
>
> Webpage error details
>
> User Agent
Ah bewdy! Thanks.
>-Original Message-
>From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
>Sent: Saturday, 17 September 2011 3:16 PM
>To: users@wicket.apache.org
>Subject: Re: BookmarkablePageRequestTarget not available in 1.5
>
>even in 1.4 this can be rewritten as rc.setresponsepage(pa
