wicket form and browser back
hello, I know that is an ongoing discussion point for years but nevertheless I would like to ask you whether there are good solutions in the meantime. In my web application (WICKET 6.5) there is a quite big form and I want to detect and react when a user goes back to an older version of this form using the browser back button. When the user hits the submit button on that older version he will lose data. I would like to avoid that in some way. Suggestions and experiences are very welcome. Many thanks in advance Karl-Heinz - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket form and browser back
Hi, Mark the page as non-versioned (Page.setVersioned(false)). This way there won't be previous version of page. When the user uses browser back button she will go to the previous page, not to the previous version of the current page. On Tue, Oct 1, 2013 at 9:35 AM, Karl-Heinz Golz karl-heinz.g...@t-online.de wrote: hello, I know that is an ongoing discussion point for years but nevertheless I would like to ask you whether there are good solutions in the meantime. In my web application (WICKET 6.5) there is a quite big form and I want to detect and react when a user goes back to an older version of this form using the browser back button. When the user hits the submit button on that older version he will lose data. I would like to avoid that in some way. Suggestions and experiences are very welcome. Many thanks in advance Karl-Heinz - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket-bootstrap Bootstrap 3 support
hi, i've fixed wicket-webjars and pushed a new version (0.3.0) to maven central. https://github.com/l0rdn1kk0n/wicket-webjars/releases/tag/wicket-webjars-0.3.0 i've also deployed a new 0.9.0-SNAPSHOT version of wicket-bootstrap that uses wicket-webjars 0.3.0. Michael Am 26.09.2013 um 11:42 schrieb Martin Grigorov mgrigo...@apache.org : Hi, Please file an issue. I think the main problem here is the usage of webjars. bootstrap.(css|js) are loaded from webjars-bootstrap.jar that contains all resources, including the fonts. But for some reason the resolving doesn't work. The same issue can been seen with the samples application when any non-bootswatch theme is used. On Thu, Sep 26, 2013 at 11:12 AM, Marcel Hoerr marcel.ho...@gmx.de wrote: hi, i replaced the my 0.8.x version with the new 0.9.0-SNAPSHOT and get the following error: WARN - WicketObjects - Could not resolve class [fonts] java.lang.ClassNotFoundException: fonts Actually this font can not be loaded: fonts/glyphicons-halflings-regular.woff I found this thread on stackoverflow, which indicated that there is a problem with bootstraps customizer tool: http://stackoverflow.com/questions/18369036/bootstrap-3-glyphicons-not-working Does wicket-bootstrap use customized themes (and therefor not all/wrong fonts or icons have been attached to wicket-bootstrap)? best reagards marcel Gesendet: Mittwoch, 25. September 2013 um 15:28 Uhr Von: Michael Haitz michael.ha...@1und1.de An: users@wicket.apache.org users@wicket.apache.org Betreff: Re: Wicket-bootstrap Bootstrap 3 support Hi, i've deployed a 0.9.0-SNAPSHOT to sonatype this morning ;) dependency groupIdde.agilecoders.wicket/groupId artifactIdwicket-bootstrap-core/artifactId version0.9.0-SNAPSHOT/version /dependency cheers, Michael Am 25.09.2013 um 14:24 schrieb David Beer david.m.b...@gmail.com: Hi All I am looking at using Bootstrap 3 for our next webapplication layout. I have used 2.3.2 with success and the Wicket-Bootstrap project. I just wondered what the status is of the support for BS3 before I start coding the initial layout. Or am I better sticking with BS2 for now and upgrading once Wicket-Bootstrap for BS3 is released. Thanks David - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket form and browser back
Thank you, Martin, that works well. But next question: when a user goes back and forward via browser back and forward buttons, then already filled in fields will be empty (using Firefox). Is it possible to handle browser back the same way like form submit? That is, browser back causes a trip to the server and wicket gives controll to my application the same way it would be done when the user presses the submit button? Am 01.10.2013 09:59, schrieb Martin Grigorov: Hi, Mark the page as non-versioned (Page.setVersioned(false)). This way there won't be previous version of page. When the user uses browser back button she will go to the previous page, not to the previous version of the current page. On Tue, Oct 1, 2013 at 9:35 AM, Karl-Heinz Golz karl-heinz.g...@t-online.de wrote: hello, I know that is an ongoing discussion point for years but nevertheless I would like to ask you whether there are good solutions in the meantime. In my web application (WICKET 6.5) there is a quite big form and I want to detect and react when a user goes back to an older version of this form using the browser back button. When the user hits the submit button on that older version he will lose data. I would like to avoid that in some way. Suggestions and experiences are very welcome. Many thanks in advance Karl-Heinz - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket form and browser back
I'm not sure this is possible. But you can use AjaxFormComponentUpdatingBehavior(change) to update the server state once a form component is changed at the client side. On Tue, Oct 1, 2013 at 10:53 AM, Karl-Heinz Golz karl-heinz.g...@t-online.de wrote: Thank you, Martin, that works well. But next question: when a user goes back and forward via browser back and forward buttons, then already filled in fields will be empty (using Firefox). Is it possible to handle browser back the same way like form submit? That is, browser back causes a trip to the server and wicket gives controll to my application the same way it would be done when the user presses the submit button? Am 01.10.2013 09:59, schrieb Martin Grigorov: Hi, Mark the page as non-versioned (Page.setVersioned(false)). This way there won't be previous version of page. When the user uses browser back button she will go to the previous page, not to the previous version of the current page. On Tue, Oct 1, 2013 at 9:35 AM, Karl-Heinz Golz karl-heinz.g...@t-online.de wrote: hello, I know that is an ongoing discussion point for years but nevertheless I would like to ask you whether there are good solutions in the meantime. In my web application (WICKET 6.5) there is a quite big form and I want to detect and react when a user goes back to an older version of this form using the browser back button. When the user hits the submit button on that older version he will lose data. I would like to avoid that in some way. Suggestions and experiences are very welcome. Many thanks in advance Karl-Heinz - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket form and browser back
AFAIK does a browser back bypass everything on the page. Maybe it is better to avoid paging if there is dependent state on different pages (use ajax instead and make it single-page). michael:) Am 01.10.13 10:53, schrieb Karl-Heinz Golz: Thank you, Martin, that works well. But next question: when a user goes back and forward via browser back and forward buttons, then already filled in fields will be empty (using Firefox). Is it possible to handle browser back the same way like form submit? That is, browser back causes a trip to the server and wicket gives controll to my application the same way it would be done when the user presses the submit button? Am 01.10.2013 09:59, schrieb Martin Grigorov: Hi, Mark the page as non-versioned (Page.setVersioned(false)). This way there won't be previous version of page. When the user uses browser back button she will go to the previous page, not to the previous version of the current page. On Tue, Oct 1, 2013 at 9:35 AM, Karl-Heinz Golz karl-heinz.g...@t-online.de wrote: hello, I know that is an ongoing discussion point for years but nevertheless I would like to ask you whether there are good solutions in the meantime. In my web application (WICKET 6.5) there is a quite big form and I want to detect and react when a user goes back to an older version of this form using the browser back button. When the user hits the submit button on that older version he will lose data. I would like to avoid that in some way. Suggestions and experiences are very welcome. Many thanks in advance Karl-Heinz - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
How do I disable GZip compression in Wicket 6?
Hi, In Wicket 1.4.22 I used to be able to disable GZip compression like this: WebApplication.getResourceSettings().setDisableGZipCompression(true); That way seems to be removed in 6 and I can't find anything in the migration guides regarding this. Have anyone else stumbled upon this and have any advice? /Marcus Marcus Ludvigsson mobile: +4670 78 10 259 | mar...@lubbit.se | http://www.lubbit.se
Re: wicket form and browser back
Thank you Martin and Michael. I will try that and hope, the combination of setVersioned(false) and using AJAX for all form components will solve my problem. Am 01.10.2013 11:57, schrieb Michael Mosmann: AFAIK does a browser back bypass everything on the page. Maybe it is better to avoid paging if there is dependent state on different pages (use ajax instead and make it single-page). michael:) Am 01.10.2013 11:08, schrieb Martin Grigorov: I'm not sure this is possible. But you can use AjaxFormComponentUpdatingBehavior(change) to update the server state once a form component is changed at the client side. Am 01.10.13 10:53, schrieb Karl-Heinz Golz: Thank you, Martin, that works well. But next question: when a user goes back and forward via browser back and forward buttons, then already filled in fields will be empty (using Firefox). Is it possible to handle browser back the same way like form submit? That is, browser back causes a trip to the server and wicket gives controll to my application the same way it would be done when the user presses the submit button? Am 01.10.2013 09:59, schrieb Martin Grigorov: Hi, Mark the page as non-versioned (Page.setVersioned(false)). This way there won't be previous version of page. When the user uses browser back button she will go to the previous page, not to the previous version of the current page. On Tue, Oct 1, 2013 at 9:35 AM, Karl-Heinz Golz karl-heinz.g...@t-online.de wrote: hello, I know that is an ongoing discussion point for years but nevertheless I would like to ask you whether there are good solutions in the meantime. In my web application (WICKET 6.5) there is a quite big form and I want to detect and react when a user goes back to an older version of this form using the browser back button. When the user hits the submit button on that older version he will lose data. I would like to avoid that in some way. Suggestions and experiences are very welcome. Many thanks in advance Karl-Heinz - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: How do I disable GZip compression in Wicket 6?
Hi, This setting has been removed with 1.5.0. Wicket does not compress the response anymore. If compression is needed then the application can use either web container's settings or a custom Servlet Filter. So you have nothing to do. Just remove this line from your config. On Tue, Oct 1, 2013 at 4:17 PM, Marcus Ludvigsson mar...@lubbit.se wrote: Hi, In Wicket 1.4.22 I used to be able to disable GZip compression like this: WebApplication.getResourceSettings().setDisableGZipCompression(true); That way seems to be removed in 6 and I can't find anything in the migration guides regarding this. Have anyone else stumbled upon this and have any advice? /Marcus Marcus Ludvigsson mobile: +4670 78 10 259 | mar...@lubbit.se | http://www.lubbit.se
RE: How do I disable GZip compression in Wicket 6?
Hey Karl, Would you kindly update the migration wiki page for the rest of us? ~ Thank you, Paul Bors -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: Tuesday, October 01, 2013 10:20 AM To: users@wicket.apache.org Subject: Re: How do I disable GZip compression in Wicket 6? Hi, This setting has been removed with 1.5.0. Wicket does not compress the response anymore. If compression is needed then the application can use either web container's settings or a custom Servlet Filter. So you have nothing to do. Just remove this line from your config. On Tue, Oct 1, 2013 at 4:17 PM, Marcus Ludvigsson mar...@lubbit.se wrote: Hi, In Wicket 1.4.22 I used to be able to disable GZip compression like this: WebApplication.getResourceSettings().setDisableGZipCompression(true); That way seems to be removed in 6 and I can't find anything in the migration guides regarding this. Have anyone else stumbled upon this and have any advice? /Marcus Marcus Ludvigsson mobile: +4670 78 10 259 | mar...@lubbit.se | http://www.lubbit.se - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: how to connect elements - label and input (checkbox)
I found this searching for the same answer and my existing code was: input type=checkbox wicket:id=acceptTerms/ label wicket:for=acceptTermsI agree to the terms/label but the output is: input type=checkbox name=acceptTerms id=acceptTerms5/ label for=acceptTerms5I agree to the terms/label but sometimes it seems that the id isn't set on the checkbox. I'm still trying to figure out why. (using 6.10 still) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/how-to-connect-elements-label-and-input-checkbox-tp4650304p4661648.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: how to connect elements - label and input (checkbox)
aha! it seems that the first time it renders it doesn't include the id in the checkbox. when it fails validation, the id appears and the label works as expected. i'll dig into the code when i get a chance. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/how-to-connect-elements-label-and-input-checkbox-tp4650304p4661649.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
