the most authorative might be the javadoc in the code:
http://fisheye6.atlassian.com/browse/wicket/trunk/wicket/src/main/java/org/apache/wicket/settings/IPageSettings.java?r=768578#l53
mf
Am 05.05.2009 um 00:25 schrieb Eyal Golan:
In short,
what does it mean exactly Multi Window Support ?
thanks Martin.
Eyal Golan
egola...@gmail.com
Visit: http://jvdrums.sourceforge.net/
LinkedIn: http://www.linkedin.com/in/egolan74
P Save a tree. Please don't print this e-mail unless it's really necessary
On Tue, May 5, 2009 at 10:28 AM, Martin Funk mafulaf...@googlemail.comwrote:
the most
maybe automatic multi window support might help you
this can be turned on like this in the init method of your Application.
/**
* @see org.apache.wicket.protocol.http.WebApplication#init()
*/
@Override
protected void init()
{
I think I would use Martins idea + markup inheritance (pages that are
aware of the required parameters etc)...
2009/5/3 Matthew Welch matt...@welchkin.net:
The data in the application that I'm working on is divided in any number of
different contexts. The pages displayed for each context are
I'm not worried about the multiple window thing. FWIW I believe that value is
set to true by default anyway. I'm just wondering if there's a way to add a
parameter to each link on page to ensure that the next page stays in the
same context.
For instance, when I was trying to solve an unrelated
you can provide your own subclass of webresponse and override
encodeurl the same way. see WebApplication#newWebResponse
-igor
On Mon, May 4, 2009 at 2:25 PM, Matt Welch matt...@welchkin.net wrote:
I'm not worried about the multiple window thing. FWIW I believe that value is
set to true by
In short,
what does it mean exactly Multi Window Support ?
Eyal Golan
egola...@gmail.com
Visit: http://jvdrums.sourceforge.net/
LinkedIn: http://www.linkedin.com/in/egolan74
P Save a tree. Please don't print this e-mail unless it's really necessary
On Mon, May 4, 2009 at 1:06 PM, Martin Funk
igor.vaynberg wrote:
you can provide your own subclass of webresponse and override
encodeurl the same way. see WebApplication#newWebResponse
-igor
Thanks. That's exactly the kind of thing I was looking for. I'll look into
it.
-Matt
--
View this message in context:
