Martin,
Awesome - thanks, once again...!
That gives me plenty to get on with... :)
Cheers,
Col.
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: 27 May 2013 17:34
To: users@wicket.apache.org
Subject: Re: Panel switching
Hi,
I guess you know that History
Hi Maxim,
For Wicket the client is the proxy, so the request url is what the proxy
sends to the servlet container.
If the proxy sets the original url in a request header then the application
code can read this header and use it.
On Mon, May 27, 2013 at 10:37 AM, Maxim Solodovnik wrote:
> Hello
Hello Martin,
Is it possible to know current URL (used by the user if reverse proxy is
used)?
On Mon, May 27, 2013 at 2:34 PM, Martin Grigorov wrote:
> Hi,
>
> I guess you know that History API (pushState) works only in IE10, all older
> versions of IE do not support it.
>
> About your question
Hi,
I guess you know that History API (pushState) works only in IE10, all older
versions of IE do not support it.
About your question: you can use AjaxRequestTarget#addChildren(getPage(),
AbstractLink.class) to add all links in the current page to be repainted.
Wicket uses getRequestCycle().getUr
Andreas Bürgel (Bucyrus) wrote:
>
> Im using a org.apache.wicket.extensions.markup.html.tree.Tree now instead
> of a LinkTree. This seems to work.
> Don't forget to call "setOutputMarkupId ( true)" for all panels before
> they get displayed.
>
I forgot to say that had to add the panel to the
Im using a org.apache.wicket.extensions.markup.html.tree.Tree now instead of
a LinkTree. This seems to work.
Don't forget to call "setOutputMarkupId ( true)" for all panels before they
get displayed.
--
View this message in context:
http://www.nabble.com/Panel-switching-in-LinkTree.onNodeLinkCli
We use ReallySimpleHistory
(http://code.google.com/p/reallysimplehistory/) for this. Every AjaxLink
(or component+AjaxEventBehavior) records the url of the current page +
some indicator in the hash path (e.g. '../blah/page#someId') in rsh.js
(via AjaxCallDecorator).
Later when the user presses 'ba
will try that. tks
On Thu, Jun 26, 2008 at 4:16 PM, Thomas Mäder <[EMAIL PROTECTED]> wrote:
> Hmhhh... isn't there a Javascript function which allows to replace the URL
> of the current page in the history? I'm not sure this would work, but
> couldn't you try this:
>
> 1) replace the panel
> 2) r
Hmhhh... isn't there a Javascript function which allows to replace the URL
of the current page in the history? I'm not sure this would work, but
couldn't you try this:
1) replace the panel
2) reload the IFrame
3) now manipulate the browser history to point to the currect URL for the
current page v
yes, I know, I'm trying to figure out a solution myself.
I was sure though somebody else ran into this. :)
On Thu, Jun 26, 2008 at 3:28 PM, Thomas Mäder <[EMAIL PROTECTED]> wrote:
> Aha, the problem is that ajax does not cause a history entry to be created.
> I've seen workarounds for this (not
Aha, the problem is that ajax does not cause a history entry to be created.
I've seen workarounds for this (not with wicket, though) which reload a
hidden IFrame each time they make a relevant change. I can't see right now
how that helps you in wicket, tough.
Thomas
On Thu, Jun 26, 2008 at 1:56
yes, with Ajax
On Thu, Jun 26, 2008 at 2:15 PM, Thomas Mäder <[EMAIL PROTECTED]> wrote:
> I would expect that to happen by default. Replacing a panel should create a
> new page version which should change the Page URL. Are you using AJAX?
>
> Thomas
>
> On Thu, Jun 26, 2008 at 10:07 AM, Cristi Ma
I would expect that to happen by default. Replacing a panel should create a
new page version which should change the Page URL. Are you using AJAX?
Thomas
On Thu, Jun 26, 2008 at 10:07 AM, Cristi Manole <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> I am implementing navigation through my application by
13 matches
Mail list logo
