_
From: Maxim Solodovnik [solomax...@gmail.com]
Sent: 26 August 2013 01:22
To: users@wicket.apache.org
Subject: Re: wicket single page application: replacing panels with ajax and
back button support
we did it in Apache Openmeetings project
https://svn.apache.org/repos/asf/openmeetings/trunk/singl
we did it in Apache Openmeetings project
https://svn.apache.org/repos/asf/openmeetings/trunk/singlewebapp/src/main/java/org/apache/openmeetings/web/
not sure if it can be used as an example :) but it is working :)
On Sun, Aug 25, 2013 at 5:54 PM, Ilkka Seppälä wrote:
> Hi,
>
> I'm guessing thi
Hi,
I'm guessing this is a common way to use Wicket but could not find solution.
I want to create a single page application where navigation causes panels
to be replaced with ajax. But the immediate problem that rises is how to
make these different views bookmarkable and how to make browser's bac
i have to do something different to manage version in different browser?
i have also attached the screenshot for the same
http://apache-wicket.1842946.n4.nabble.com/file/n4652025/ref.jpg
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Back-Button-Support-Not
I have now created an issue on jira with the actual problems described above.
https://issues.apache.org/jira/browse/WICKET-4182
https://issues.apache.org/jira/browse/WICKET-4182
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Multi-tabs-and-back-button-support-1-5
i write my application as a single page then our back button
>>> support is completely hosed. i should be able to back button and
>>> re-submit the form.
>>
>> As single page - i.e. completely Ajax navigation ?
>> In this case back button support is on your own.
>&
e from using the
>> page. if i write my application as a single page then our back button
>> support is completely hosed. i should be able to back button and
>> re-submit the form.
>
> As single page - i.e. completely Ajax navigation ?
> In this case back button suppor
On Thu, Oct 27, 2011 at 5:48 PM, Igor Vaynberg wrote:
> hrm. i dont think the rendercount should prevent me from using the
> page. if i write my application as a single page then our back button
> support is completely hosed. i should be able to back button and
> re-submit the form
hrm. i dont think the rendercount should prevent me from using the
page. if i write my application as a single page then our back button
support is completely hosed. i should be able to back button and
re-submit the form.
-igor
On Thu, Oct 27, 2011 at 3:20 AM, Martin Grigorov wrote:
> The o
e on back-button and changing values.
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Multi-tabs-and-back-button-support-1-5-2-tp3943445p3943856.html
> Sent from the Users forum mailing li
I would actually like to accept the data from both tabs as long as they are
valid.
The same effect should be available on back-button and changing values.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Multi-tabs-and-back-button-support-1-5-2-tp3943445p3943856.html
Hi,
I think Page.renderCount is what stops the storing of the values.
This flag indicates that the page the user uses is stale, i.e. there
is another render of the same page happened after.
The actual check is in PageProvider class.
I don't see any clean solution for now.
What should happen if t
We are developing an application with forms and currently using wicket
1.4.18.
There are primarily two issues that we are struggeling with when upgrading
to wicket 1.5.2.
Let's say we open Page A in two tabs, first Tab1 and then Tab2. If we fill
the form in Tab1 and submit it will be valid data
Good, in this way it works.
I'm apply the onBeforeRender trick to propagate the previous state in the
session.
Thank guys, long live to Wicket
Paolo
On Thu, Dec 11, 2008 at 6:27 PM, Igor Vaynberg wrote:
> or instead of pages use panels as content. that way you use the same
> menu instance acr
or instead of pages use panels as content. that way you use the same
menu instance across multiple "pages" and the menu can keep its own
state.
-igor
On Thu, Dec 11, 2008 at 2:37 AM, Paolo Di Tommaso
wrote:
> Nice question. Consider the following use case:
>
> You have the main application menu
Nice question. Consider the following use case:
You have the main application menu bar. The user chooses an item from it.
What happens is that all the following pages will be related to that choice,
for example the second level menu in the page (that is contextual to the
above choice) and I would
No. You have to track the changes yourself. Or use Page as the scope.
What's the reason to put values in session anyway?
-Matej
On Wed, Dec 10, 2008 at 11:18 PM, Paolo Di Tommaso
<[EMAIL PROTECTED]> wrote:
> Dear community,
>
> I'm facing with a really ugly problem. In my web app I need to store
Dear community,
I'm facing with a really ugly problem. In my web app I need to store some
variables in the Wicket session.
But this cause some nasty side-effects when users click on the browser back
button.
The page displays the previous content correctly but some components, which
model is base
ROTECTED]>
> wrote:
>
>> Been reading about wicket and would want to know the context in which the
>> back button problem is being talked about..the only problem i have faced
>> with respect to back button is the double form submission, cant frame
>> myself
>>
It would be nice if an example of such ui interactions could be given...
On Mon, Mar 17, 2008 at 4:57 PM, Java Developer <[EMAIL PROTECTED]>
wrote:
> Been reading about wicket and would want to know the context in which the
> back button problem is being talked about..the only problem i have face
s being talked about..the only problem i have faced
> > with respect to back button is the double form submission, cant frame
> > myself in the right context...Can someone give a real life example of what
> > problem can a back button cause and how does versioning resolves it..
>
button cause and how does versioning resolves it..
>
>
--
View this message in context:
http://www.nabble.com/Back-button-support-tp16111425p16112197.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To
Been reading about wicket and would want to know the context in which the
back button problem is being talked about..the only problem i have faced
with respect to back button is the double form submission, cant frame myself
in the right context...Can someone give a real life example of what problem
23 matches
Mail list logo
