Re: Wicket back button behavior

[Entropy]

Hmmm, it's not quite PERFECTLY what I was after, but it may be "close
enough".  When I go back, I am still taken to previous pages by virtue of
the mounted URLs, but I am no longer being taken to old VERSIONS of those
pages, which was the main problem.  

I'll have to check with my requirements team to verify that this is close
enough.  Thanks for the suggestion and quick reply!

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-back-button-behavior-tp4677587p4677651.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: Wicket back button behavior

[Zala Pierre GOUPIL]

Hi,

If I get you right, you want to be able to have some pages that always
display their last state, right? What about trying the "Wicket no version
mapper" pattern? [1]

For you, getting rid of the version number in the URL is just a
side-effect, but it should do the trick. Plus, you can switch it on or off
on a per-page basis.

Sorry if I misunderstood you.

Regards,

Zala



1: http://stackoverflow.com/questions/8602489/delete-version-number-in-url



On Mon, Apr 10, 2017 at 8:08 PM, Entropy  wrote:

> I am trying to set this up.  I looked at some docs and I feel like
> creating a
> custom PageManager seems like what I want to do.  The thing is, no matter
> how I implement the getPage(int), the Wicket app behaves the same.  The
> back
> button still does it's default behavior every time.
>
> Here's what I did.  I capture the maximum page in touchPage(), and then
> getPage() returns it.  When I hit back during my process flow, initially I
> get a bunch of calls to getPage() which dutifully returns the currentPage I
> want.  But then, after that, touchPage is called with the prior page (the
> one the user is going BACK to).  What's more, it's called with an ID one
> GREATER than the maximum page ID as returned in getPage().
>
> getPage() is never called again in that request, and the app then renders
> the prior page, as if it ignored what getPage() returned.  It's like I am
> missing an additional change setting that would make touchPage() cooperate.
>
> I also tried raising a RestartResponseException from within the PageManager
> when BACK was hit, but that just got me sent to the error page.
>
> I overrode just the PageManager since I don't want to change how pages a
> created, just how they are re-used.  That's why i differed from
> SinglePageManager.  Am I doing anything obviously wrong?  It's all pretty
> simple right now.  i started small to try to build the complexity as I
> went,
> but since nothing I do actually changes the app behavior, I seem stuck.
>
> --
> View this message in context: http://apache-wicket.1842946.
> n4.nabble.com/Wicket-back-button-behavior-tp4677587p4677649.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
>
>


-- 
Je n'aime pas seulement ma vie, mais aussi celle des autres.

(Blade Runner)

Re: Wicket back button behavior

[Entropy]

I am trying to set this up.  I looked at some docs and I feel like creating a
custom PageManager seems like what I want to do.  The thing is, no matter
how I implement the getPage(int), the Wicket app behaves the same.  The back
button still does it's default behavior every time.

Here's what I did.  I capture the maximum page in touchPage(), and then
getPage() returns it.  When I hit back during my process flow, initially I
get a bunch of calls to getPage() which dutifully returns the currentPage I
want.  But then, after that, touchPage is called with the prior page (the
one the user is going BACK to).  What's more, it's called with an ID one
GREATER than the maximum page ID as returned in getPage().

getPage() is never called again in that request, and the app then renders
the prior page, as if it ignored what getPage() returned.  It's like I am
missing an additional change setting that would make touchPage() cooperate.  

I also tried raising a RestartResponseException from within the PageManager
when BACK was hit, but that just got me sent to the error page.  

I overrode just the PageManager since I don't want to change how pages a
created, just how they are re-used.  That's why i differed from
SinglePageManager.  Am I doing anything obviously wrong?  It's all pretty
simple right now.  i started small to try to build the complexity as I went,
but since nothing I do actually changes the app behavior, I seem stuck.

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Wicket-back-button-behavior-tp4677587p4677649.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: Weird CSS warning in IE

[Maxim Solodovnik]

Hello Sebastien,

I was able to see it in our application, I'll try to create small
application with this issue

On Mon, Apr 10, 2017 at 9:16 PM, Sebastien  wrote:

> Hi Maxim,
>
> I activated the developer tools in IE but I can't see this behavior from
> the demo site. Is there anything else to do or a special page to go?
>
> Thanks,
> Sebastien.
>
>
>
> On Sat, Apr 8, 2017 at 12:06 PM, Maxim Solodovnik 
> wrote:
>
>> Thanks a lot!
>>
>> On Sat, Apr 8, 2017 at 5:04 PM, Sebastien  wrote:
>>
>>> Hi Maxim,
>>>
>>> I will check on monday with IE...
>>>
>>> Thanks & best regards,
>>> Sebastien.
>>>
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>


-- 
WBR
Maxim aka solomax

Re: Weird CSS warning in IE

[Sebastien]

Hi Maxim,

I activated the developer tools in IE but I can't see this behavior from
the demo site. Is there anything else to do or a special page to go?

Thanks,
Sebastien.


On Sat, Apr 8, 2017 at 12:06 PM, Maxim Solodovnik 
wrote:

> Thanks a lot!
>
> On Sat, Apr 8, 2017 at 5:04 PM, Sebastien  wrote:
>
>> Hi Maxim,
>>
>> I will check on monday with IE...
>>
>> Thanks & best regards,
>> Sebastien.
>>
>>
>
>
> --
> WBR
> Maxim aka solomax
>

Re: "/websocket/closed" is not working in IE11

[Maxim Solodovnik]

Weird enough, quickstart works :(
Investigation only begins :)

On Mon, Apr 10, 2017 at 2:04 AM, Martin Grigorov 
wrote:

> On Sat, Apr 8, 2017 at 11:41 AM, Maxim Solodovnik 
> wrote:
>
> > Hello All,
> >
> > I just have noticed "/websocket/closed" is not working in IE11
> > handler set via
> > Wicket.Event.subscribe("/websocket/closed", function() {})
> > Is not fired
> >
> > The following message displayed in console instead:
> > SCRIPT12030: WebSocket Error: Network Error 12030, The connection with
> the
> > server was terminated abnormally
> >
> > Wicket: 8.0.0-M5
> > OS: Win7/Win10
> > Browser: IE11/Edge
> >
> > Should I file JIRA?
> >
>
> Yes, with a quickstart please!
>
>
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>



-- 
WBR
Maxim aka solomax

Re: POST request on textfield when expecting GET on link in AjaxPagingNavigator

[Martin Grigorov]

You can override it use only "inputchange" event for this TextField.
See
https://github.com/apache/wicket/blob/5f4affeb62bbd4ec6286394e0572ec20633c939f/wicket-core/src/main/java/org/apache/wicket/ajax/form/OnChangeAjaxBehavior.java#L79

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Mon, Apr 10, 2017 at 9:08 AM, ssamarin  wrote:

> We've got .add(new OnChangeAjaxBehavior() on TextField.
>
> Is there any way to fix this?
>
> --
> View this message in context: http://apache-wicket.1842946.
> n4.nabble.com/POST-request-on-textfield-when-expecting-GET-on-link-in-
> AjaxPagingNavigator-tp4677619p4677638.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: Constant for Jquery3

[Maxim Solodovnik]

https://issues.apache.org/jira/browse/WICKET-6354
https://github.com/apache/wicket/pull/218

On Mon, Apr 10, 2017 at 2:02 AM, Martin Grigorov 
wrote:

> We will need a new ticket!
> Pull requests are welcome :-)
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Sat, Apr 8, 2017 at 11:57 AM, Maxim Solodovnik 
> wrote:
>
> > Yep, I'm aware of 6341
> > This is why I have asked this question :)
> >
> > +1 for resource reference!
> > Currently I have to use: following code:
> > getJavaScriptLibrarySettings().setJQueryReference(new
> > JavaScriptResourceReference(DynamicJQueryResourceReference.class,
> > DynamicJQueryResourceReference.VERSION_2));
> >
> >
> > On Sat, Apr 8, 2017 at 4:55 PM, Sebastien  wrote:
> >
> > > Hi Maxim,
> > >
> > > No I don't think so: WICKET-6341 [1] has been postponed and I don't see
> > any
> > > commit about it.
> > > That said, it might be a good idea to already have the resource
> reference
> > > in wicket so anyone can quickly give a try to jQuery3
> > >
> > > [1] https://issues.apache.org/jira/browse/WICKET-6341
> > >
> > > Best regards,
> > > Sebastien.
> > >
> > > On Sat, Apr 8, 2017 at 11:18 AM, Maxim Solodovnik <
> solomax...@gmail.com>
> > > wrote:
> > >
> > > > Hello All,
> > > >
> > > > Is there constant for jquery3 in wicket?
> > > >
> > > > --
> > > > WBR
> > > > Maxim aka solomax
> > > >
> > >
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>



-- 
WBR
Maxim aka solomax

Re: POST request on textfield when expecting GET on link in AjaxPagingNavigator

[ssamarin]

We've got .add(new OnChangeAjaxBehavior() on TextField. 

Is there any way to fix this?

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/POST-request-on-textfield-when-expecting-GET-on-link-in-AjaxPagingNavigator-tp4677619p4677638.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