You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Martin Grigorov <mg...@apache.org> on 2015/04/17 22:54:16 UTC
Wicket Ajax debug window usefulness?
Hi,
Do you still use Wicket Ajax Debug window for something when developing
your applications?
I haven't used it in few years now and it seems I don't miss it.
I can see all the debug information in the browser's dev tools:
- ajax response in the Network tab
- info and error messages in the JS Console tab
Is there something that makes it still useful or we can drop it for Wicket
8?
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
Re: Wicket Ajax debug window usefulness?
Posted by Tobias Soloschenko <to...@googlemail.com>.
Then +1 to drop it. :-)
kind regards
Tobias
> Am 20.04.2015 um 13:31 schrieb Martin Grigorov <mg...@apache.org>:
>
> Hi,
>
> On Mon, Apr 20, 2015 at 12:42 PM, Tobias Soloschenko <
> tobiassoloschenko@googlemail.com> wrote:
>
>> Hi,
>>
>> Ok this solution sounds good to me:
>>
>> * Flag for info / error
>> * Log into console
>> * Ajax Response via Network Tab in Browsers
>>
>> Thanks for your explanations! :-)
>>
>> One little question: what about IE6? There is no console object available
>> - do you mind to drop the support for that browser in wicket 8?
>
> I am not sure this is documented officially somewhere but AFAIR we support
> IE8+ since Wicket 6.0.0.
>
>
>>
>> I don't know the current version of wicket's jquery version.
>>
>> As of the docs of jquery about IE:
>>
>> jQuery 1.x - IE 6+
>> jQuery 2.x - IE 9+
>
> Thanks to jQuery we didn't have any bug reports against specific version of
> a browser.
>
>
>>
>> kind regards
>>
>> Tobias
>>
>>> Am 20.04.2015 um 09:05 schrieb Martin Grigorov <mg...@apache.org>:
>>>
>>> Hi Tobias,
>>>
>>> The debug api of wicket-ajax-jquery.js is: Wicket.Log.(info|error).
>>> If the debug window is enabled then both methods log in the debug window
>>> and in the JS window.console.
>>> If the debug window is disabled then only Wicket.Log.error is enabled and
>>> logs in the JS window.console.
>>>
>>> IMO we can drop the debug window and replace with with a boolean switch
>>> that enables logging of INFO messages in the JS console. The INFO message
>>> with the XML response should be removed too because this information is
>>> available in the Network tab
>>>
>>>
>>> On Sat, Apr 18, 2015 at 12:39 AM, Tobias Soloschenko <
>>> tobiassoloschenko@googlemail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> please don't drop it because of focus requests and some other debug
>>>> information of actions requested on server side - server actions can't
>> be
>>>> logged at client side, but with the debug window.
>>>>
>>>> kind regards
>>>>
>>>> Tobias
>>>>
>>>>> Am 17.04.2015 um 22:54 schrieb Martin Grigorov <mg...@apache.org>:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Do you still use Wicket Ajax Debug window for something when developing
>>>>> your applications?
>>>>>
>>>>> I haven't used it in few years now and it seems I don't miss it.
>>>>> I can see all the debug information in the browser's dev tools:
>>>>> - ajax response in the Network tab
>>>>> - info and error messages in the JS Console tab
>>>>>
>>>>> Is there something that makes it still useful or we can drop it for
>>>> Wicket
>>>>> 8?
>>>>>
>>>>> Martin Grigorov
>>>>> Wicket Training and Consulting
>>>>> https://twitter.com/mtgrigorov
>>
Re: Wicket Ajax debug window usefulness?
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
On Mon, Apr 20, 2015 at 12:42 PM, Tobias Soloschenko <
tobiassoloschenko@googlemail.com> wrote:
> Hi,
>
> Ok this solution sounds good to me:
>
> * Flag for info / error
> * Log into console
> * Ajax Response via Network Tab in Browsers
>
> Thanks for your explanations! :-)
>
> One little question: what about IE6? There is no console object available
> - do you mind to drop the support for that browser in wicket 8?
>
I am not sure this is documented officially somewhere but AFAIR we support
IE8+ since Wicket 6.0.0.
>
> I don't know the current version of wicket's jquery version.
>
> As of the docs of jquery about IE:
>
> jQuery 1.x - IE 6+
> jQuery 2.x - IE 9+
>
Thanks to jQuery we didn't have any bug reports against specific version of
a browser.
>
> kind regards
>
> Tobias
>
> > Am 20.04.2015 um 09:05 schrieb Martin Grigorov <mg...@apache.org>:
> >
> > Hi Tobias,
> >
> > The debug api of wicket-ajax-jquery.js is: Wicket.Log.(info|error).
> > If the debug window is enabled then both methods log in the debug window
> > and in the JS window.console.
> > If the debug window is disabled then only Wicket.Log.error is enabled and
> > logs in the JS window.console.
> >
> > IMO we can drop the debug window and replace with with a boolean switch
> > that enables logging of INFO messages in the JS console. The INFO message
> > with the XML response should be removed too because this information is
> > available in the Network tab
> >
> >
> > On Sat, Apr 18, 2015 at 12:39 AM, Tobias Soloschenko <
> > tobiassoloschenko@googlemail.com> wrote:
> >
> >> Hi,
> >>
> >> please don't drop it because of focus requests and some other debug
> >> information of actions requested on server side - server actions can't
> be
> >> logged at client side, but with the debug window.
> >>
> >> kind regards
> >>
> >> Tobias
> >>
> >>> Am 17.04.2015 um 22:54 schrieb Martin Grigorov <mg...@apache.org>:
> >>>
> >>> Hi,
> >>>
> >>> Do you still use Wicket Ajax Debug window for something when developing
> >>> your applications?
> >>>
> >>> I haven't used it in few years now and it seems I don't miss it.
> >>> I can see all the debug information in the browser's dev tools:
> >>> - ajax response in the Network tab
> >>> - info and error messages in the JS Console tab
> >>>
> >>> Is there something that makes it still useful or we can drop it for
> >> Wicket
> >>> 8?
> >>>
> >>> Martin Grigorov
> >>> Wicket Training and Consulting
> >>> https://twitter.com/mtgrigorov
> >>
>
Re: Wicket Ajax debug window usefulness?
Posted by Tobias Soloschenko <to...@googlemail.com>.
Hi,
Ok this solution sounds good to me:
* Flag for info / error
* Log into console
* Ajax Response via Network Tab in Browsers
Thanks for your explanations! :-)
One little question: what about IE6? There is no console object available - do you mind to drop the support for that browser in wicket 8?
I don't know the current version of wicket's jquery version.
As of the docs of jquery about IE:
jQuery 1.x - IE 6+
jQuery 2.x - IE 9+
kind regards
Tobias
> Am 20.04.2015 um 09:05 schrieb Martin Grigorov <mg...@apache.org>:
>
> Hi Tobias,
>
> The debug api of wicket-ajax-jquery.js is: Wicket.Log.(info|error).
> If the debug window is enabled then both methods log in the debug window
> and in the JS window.console.
> If the debug window is disabled then only Wicket.Log.error is enabled and
> logs in the JS window.console.
>
> IMO we can drop the debug window and replace with with a boolean switch
> that enables logging of INFO messages in the JS console. The INFO message
> with the XML response should be removed too because this information is
> available in the Network tab
>
>
> On Sat, Apr 18, 2015 at 12:39 AM, Tobias Soloschenko <
> tobiassoloschenko@googlemail.com> wrote:
>
>> Hi,
>>
>> please don't drop it because of focus requests and some other debug
>> information of actions requested on server side - server actions can't be
>> logged at client side, but with the debug window.
>>
>> kind regards
>>
>> Tobias
>>
>>> Am 17.04.2015 um 22:54 schrieb Martin Grigorov <mg...@apache.org>:
>>>
>>> Hi,
>>>
>>> Do you still use Wicket Ajax Debug window for something when developing
>>> your applications?
>>>
>>> I haven't used it in few years now and it seems I don't miss it.
>>> I can see all the debug information in the browser's dev tools:
>>> - ajax response in the Network tab
>>> - info and error messages in the JS Console tab
>>>
>>> Is there something that makes it still useful or we can drop it for
>> Wicket
>>> 8?
>>>
>>> Martin Grigorov
>>> Wicket Training and Consulting
>>> https://twitter.com/mtgrigorov
>>
Re: Wicket Ajax debug window usefulness?
Posted by Martijn Dashorst <ma...@gmail.com>.
On Mon, Apr 20, 2015 at 2:06 PM, Martin Grigorov <mg...@apache.org> wrote:
>> developers, this is invaluable since they dont know to constantly look at
>> the server console. It would be great if that could be expanded to included
>> indications of other server side errors ( such as serialization problems ).
>
> The serialization of the page is done after the flushing of the response so
> it is a bit late.
> We can implement a new way to notify WebSocket/ServerSentEvent/AjaxPolling
> instead and show a floating div (like Growl) with the error message...
>
At €dayjob we have a behavior on the page that performs an additional
Ajax call to the server to see if there were any serialization errors
(we have extended the serialization checker with a check for Hibernate
entities), and then redirect to an error page if any serverside errors
were detected.
Martijn
Re: Wicket Ajax debug window usefulness?
Posted by Martin Grigorov <mg...@apache.org>.
On Mon, Apr 20, 2015 at 2:45 PM, Nick Pratt <nb...@gmail.com> wrote:
> One of the most helpful features of the debug window is the red flashing
> indication when there's an error detected by Wicket. For newer Wicket
>
Good point!
This is a good reason to have wicket-ajax-debug-jquery.js around.
Or we can recommend something like:
https://chrome.google.com/webstore/detail/javascript-errors-notifie/jafmfknfnkoekkdocjiaipcnmkklaajd
> developers, this is invaluable since they dont know to constantly look at
> the server console. It would be great if that could be expanded to included
> indications of other server side errors ( such as serialization problems ).
>
The serialization of the page is done after the flushing of the response so
it is a bit late.
We can implement a new way to notify WebSocket/ServerSentEvent/AjaxPolling
instead and show a floating div (like Growl) with the error message...
>
> The content of the debug window isn't that useful to us, but primarily
> because of its lack of formatting / pretty-print in the output. It would
> be more helpful as a diagnostics/development tool if it was a little
> clearer what was going on "repainting component #xyz", "executing JS..."
> rather that us having to interpret the encoding every time we want to
> figure something out.
>
>
> On Mon, Apr 20, 2015 at 7:33 AM, Martin Grigorov <mg...@apache.org>
> wrote:
>
> > Hi,
> >
> > I suggest to drop the debug window with Wicket 8.x.
> > So you all will have some time to get used with the console until then
> :-)
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> > On Mon, Apr 20, 2015 at 2:07 PM, Sebastien <se...@gmail.com> wrote:
> >
> > > Same answer as Sven, I will switch to browser's console to see if it's
> > > convenient as well..
> > >
> > > On Mon, Apr 20, 2015 at 12:59 PM, Sven Meier <sv...@meiers.net> wrote:
> > >
> > > > I'm still using the debug window, but the browser's console should do
> > > fine
> > > > too.
> > > >
> > > > Sven
> > > >
> > > >
> > > >
> > > > On 20.04.2015 09:05, Martin Grigorov wrote:
> > > >
> > > >> Hi Tobias,
> > > >>
> > > >> The debug api of wicket-ajax-jquery.js is: Wicket.Log.(info|error).
> > > >> If the debug window is enabled then both methods log in the debug
> > window
> > > >> and in the JS window.console.
> > > >> If the debug window is disabled then only Wicket.Log.error is
> enabled
> > > and
> > > >> logs in the JS window.console.
> > > >>
> > > >> IMO we can drop the debug window and replace with with a boolean
> > switch
> > > >> that enables logging of INFO messages in the JS console. The INFO
> > > message
> > > >> with the XML response should be removed too because this information
> > is
> > > >> available in the Network tab
> > > >>
> > > >>
> > > >> On Sat, Apr 18, 2015 at 12:39 AM, Tobias Soloschenko <
> > > >> tobiassoloschenko@googlemail.com> wrote:
> > > >>
> > > >> Hi,
> > > >>>
> > > >>> please don't drop it because of focus requests and some other debug
> > > >>> information of actions requested on server side - server actions
> > can't
> > > be
> > > >>> logged at client side, but with the debug window.
> > > >>>
> > > >>> kind regards
> > > >>>
> > > >>> Tobias
> > > >>>
> > > >>> Am 17.04.2015 um 22:54 schrieb Martin Grigorov <
> > mgrigorov@apache.org
> > > >:
> > > >>>>
> > > >>>> Hi,
> > > >>>>
> > > >>>> Do you still use Wicket Ajax Debug window for something when
> > > developing
> > > >>>> your applications?
> > > >>>>
> > > >>>> I haven't used it in few years now and it seems I don't miss it.
> > > >>>> I can see all the debug information in the browser's dev tools:
> > > >>>> - ajax response in the Network tab
> > > >>>> - info and error messages in the JS Console tab
> > > >>>>
> > > >>>> Is there something that makes it still useful or we can drop it
> for
> > > >>>>
> > > >>> Wicket
> > > >>>
> > > >>>> 8?
> > > >>>>
> > > >>>> Martin Grigorov
> > > >>>> Wicket Training and Consulting
> > > >>>> https://twitter.com/mtgrigorov
> > > >>>>
> > > >>>
> > > >
> > >
> >
>
Re: Wicket Ajax debug window usefulness?
Posted by Nick Pratt <nb...@gmail.com>.
One of the most helpful features of the debug window is the red flashing
indication when there's an error detected by Wicket. For newer Wicket
developers, this is invaluable since they dont know to constantly look at
the server console. It would be great if that could be expanded to included
indications of other server side errors ( such as serialization problems ).
The content of the debug window isn't that useful to us, but primarily
because of its lack of formatting / pretty-print in the output. It would
be more helpful as a diagnostics/development tool if it was a little
clearer what was going on "repainting component #xyz", "executing JS..."
rather that us having to interpret the encoding every time we want to
figure something out.
On Mon, Apr 20, 2015 at 7:33 AM, Martin Grigorov <mg...@apache.org>
wrote:
> Hi,
>
> I suggest to drop the debug window with Wicket 8.x.
> So you all will have some time to get used with the console until then :-)
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Mon, Apr 20, 2015 at 2:07 PM, Sebastien <se...@gmail.com> wrote:
>
> > Same answer as Sven, I will switch to browser's console to see if it's
> > convenient as well..
> >
> > On Mon, Apr 20, 2015 at 12:59 PM, Sven Meier <sv...@meiers.net> wrote:
> >
> > > I'm still using the debug window, but the browser's console should do
> > fine
> > > too.
> > >
> > > Sven
> > >
> > >
> > >
> > > On 20.04.2015 09:05, Martin Grigorov wrote:
> > >
> > >> Hi Tobias,
> > >>
> > >> The debug api of wicket-ajax-jquery.js is: Wicket.Log.(info|error).
> > >> If the debug window is enabled then both methods log in the debug
> window
> > >> and in the JS window.console.
> > >> If the debug window is disabled then only Wicket.Log.error is enabled
> > and
> > >> logs in the JS window.console.
> > >>
> > >> IMO we can drop the debug window and replace with with a boolean
> switch
> > >> that enables logging of INFO messages in the JS console. The INFO
> > message
> > >> with the XML response should be removed too because this information
> is
> > >> available in the Network tab
> > >>
> > >>
> > >> On Sat, Apr 18, 2015 at 12:39 AM, Tobias Soloschenko <
> > >> tobiassoloschenko@googlemail.com> wrote:
> > >>
> > >> Hi,
> > >>>
> > >>> please don't drop it because of focus requests and some other debug
> > >>> information of actions requested on server side - server actions
> can't
> > be
> > >>> logged at client side, but with the debug window.
> > >>>
> > >>> kind regards
> > >>>
> > >>> Tobias
> > >>>
> > >>> Am 17.04.2015 um 22:54 schrieb Martin Grigorov <
> mgrigorov@apache.org
> > >:
> > >>>>
> > >>>> Hi,
> > >>>>
> > >>>> Do you still use Wicket Ajax Debug window for something when
> > developing
> > >>>> your applications?
> > >>>>
> > >>>> I haven't used it in few years now and it seems I don't miss it.
> > >>>> I can see all the debug information in the browser's dev tools:
> > >>>> - ajax response in the Network tab
> > >>>> - info and error messages in the JS Console tab
> > >>>>
> > >>>> Is there something that makes it still useful or we can drop it for
> > >>>>
> > >>> Wicket
> > >>>
> > >>>> 8?
> > >>>>
> > >>>> Martin Grigorov
> > >>>> Wicket Training and Consulting
> > >>>> https://twitter.com/mtgrigorov
> > >>>>
> > >>>
> > >
> >
>
Re: Wicket Ajax debug window usefulness?
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
I suggest to drop the debug window with Wicket 8.x.
So you all will have some time to get used with the console until then :-)
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, Apr 20, 2015 at 2:07 PM, Sebastien <se...@gmail.com> wrote:
> Same answer as Sven, I will switch to browser's console to see if it's
> convenient as well..
>
> On Mon, Apr 20, 2015 at 12:59 PM, Sven Meier <sv...@meiers.net> wrote:
>
> > I'm still using the debug window, but the browser's console should do
> fine
> > too.
> >
> > Sven
> >
> >
> >
> > On 20.04.2015 09:05, Martin Grigorov wrote:
> >
> >> Hi Tobias,
> >>
> >> The debug api of wicket-ajax-jquery.js is: Wicket.Log.(info|error).
> >> If the debug window is enabled then both methods log in the debug window
> >> and in the JS window.console.
> >> If the debug window is disabled then only Wicket.Log.error is enabled
> and
> >> logs in the JS window.console.
> >>
> >> IMO we can drop the debug window and replace with with a boolean switch
> >> that enables logging of INFO messages in the JS console. The INFO
> message
> >> with the XML response should be removed too because this information is
> >> available in the Network tab
> >>
> >>
> >> On Sat, Apr 18, 2015 at 12:39 AM, Tobias Soloschenko <
> >> tobiassoloschenko@googlemail.com> wrote:
> >>
> >> Hi,
> >>>
> >>> please don't drop it because of focus requests and some other debug
> >>> information of actions requested on server side - server actions can't
> be
> >>> logged at client side, but with the debug window.
> >>>
> >>> kind regards
> >>>
> >>> Tobias
> >>>
> >>> Am 17.04.2015 um 22:54 schrieb Martin Grigorov <mgrigorov@apache.org
> >:
> >>>>
> >>>> Hi,
> >>>>
> >>>> Do you still use Wicket Ajax Debug window for something when
> developing
> >>>> your applications?
> >>>>
> >>>> I haven't used it in few years now and it seems I don't miss it.
> >>>> I can see all the debug information in the browser's dev tools:
> >>>> - ajax response in the Network tab
> >>>> - info and error messages in the JS Console tab
> >>>>
> >>>> Is there something that makes it still useful or we can drop it for
> >>>>
> >>> Wicket
> >>>
> >>>> 8?
> >>>>
> >>>> Martin Grigorov
> >>>> Wicket Training and Consulting
> >>>> https://twitter.com/mtgrigorov
> >>>>
> >>>
> >
>
Re: Wicket Ajax debug window usefulness?
Posted by Sebastien <se...@gmail.com>.
Same answer as Sven, I will switch to browser's console to see if it's
convenient as well..
On Mon, Apr 20, 2015 at 12:59 PM, Sven Meier <sv...@meiers.net> wrote:
> I'm still using the debug window, but the browser's console should do fine
> too.
>
> Sven
>
>
>
> On 20.04.2015 09:05, Martin Grigorov wrote:
>
>> Hi Tobias,
>>
>> The debug api of wicket-ajax-jquery.js is: Wicket.Log.(info|error).
>> If the debug window is enabled then both methods log in the debug window
>> and in the JS window.console.
>> If the debug window is disabled then only Wicket.Log.error is enabled and
>> logs in the JS window.console.
>>
>> IMO we can drop the debug window and replace with with a boolean switch
>> that enables logging of INFO messages in the JS console. The INFO message
>> with the XML response should be removed too because this information is
>> available in the Network tab
>>
>>
>> On Sat, Apr 18, 2015 at 12:39 AM, Tobias Soloschenko <
>> tobiassoloschenko@googlemail.com> wrote:
>>
>> Hi,
>>>
>>> please don't drop it because of focus requests and some other debug
>>> information of actions requested on server side - server actions can't be
>>> logged at client side, but with the debug window.
>>>
>>> kind regards
>>>
>>> Tobias
>>>
>>> Am 17.04.2015 um 22:54 schrieb Martin Grigorov <mg...@apache.org>:
>>>>
>>>> Hi,
>>>>
>>>> Do you still use Wicket Ajax Debug window for something when developing
>>>> your applications?
>>>>
>>>> I haven't used it in few years now and it seems I don't miss it.
>>>> I can see all the debug information in the browser's dev tools:
>>>> - ajax response in the Network tab
>>>> - info and error messages in the JS Console tab
>>>>
>>>> Is there something that makes it still useful or we can drop it for
>>>>
>>> Wicket
>>>
>>>> 8?
>>>>
>>>> Martin Grigorov
>>>> Wicket Training and Consulting
>>>> https://twitter.com/mtgrigorov
>>>>
>>>
>
Re: Wicket Ajax debug window usefulness?
Posted by Sven Meier <sv...@meiers.net>.
I'm still using the debug window, but the browser's console should do
fine too.
Sven
On 20.04.2015 09:05, Martin Grigorov wrote:
> Hi Tobias,
>
> The debug api of wicket-ajax-jquery.js is: Wicket.Log.(info|error).
> If the debug window is enabled then both methods log in the debug window
> and in the JS window.console.
> If the debug window is disabled then only Wicket.Log.error is enabled and
> logs in the JS window.console.
>
> IMO we can drop the debug window and replace with with a boolean switch
> that enables logging of INFO messages in the JS console. The INFO message
> with the XML response should be removed too because this information is
> available in the Network tab
>
>
> On Sat, Apr 18, 2015 at 12:39 AM, Tobias Soloschenko <
> tobiassoloschenko@googlemail.com> wrote:
>
>> Hi,
>>
>> please don't drop it because of focus requests and some other debug
>> information of actions requested on server side - server actions can't be
>> logged at client side, but with the debug window.
>>
>> kind regards
>>
>> Tobias
>>
>>> Am 17.04.2015 um 22:54 schrieb Martin Grigorov <mg...@apache.org>:
>>>
>>> Hi,
>>>
>>> Do you still use Wicket Ajax Debug window for something when developing
>>> your applications?
>>>
>>> I haven't used it in few years now and it seems I don't miss it.
>>> I can see all the debug information in the browser's dev tools:
>>> - ajax response in the Network tab
>>> - info and error messages in the JS Console tab
>>>
>>> Is there something that makes it still useful or we can drop it for
>> Wicket
>>> 8?
>>>
>>> Martin Grigorov
>>> Wicket Training and Consulting
>>> https://twitter.com/mtgrigorov
Re: Wicket Ajax debug window usefulness?
Posted by Martin Grigorov <mg...@apache.org>.
Hi Tobias,
The debug api of wicket-ajax-jquery.js is: Wicket.Log.(info|error).
If the debug window is enabled then both methods log in the debug window
and in the JS window.console.
If the debug window is disabled then only Wicket.Log.error is enabled and
logs in the JS window.console.
IMO we can drop the debug window and replace with with a boolean switch
that enables logging of INFO messages in the JS console. The INFO message
with the XML response should be removed too because this information is
available in the Network tab
On Sat, Apr 18, 2015 at 12:39 AM, Tobias Soloschenko <
tobiassoloschenko@googlemail.com> wrote:
> Hi,
>
> please don't drop it because of focus requests and some other debug
> information of actions requested on server side - server actions can't be
> logged at client side, but with the debug window.
>
> kind regards
>
> Tobias
>
> > Am 17.04.2015 um 22:54 schrieb Martin Grigorov <mg...@apache.org>:
> >
> > Hi,
> >
> > Do you still use Wicket Ajax Debug window for something when developing
> > your applications?
> >
> > I haven't used it in few years now and it seems I don't miss it.
> > I can see all the debug information in the browser's dev tools:
> > - ajax response in the Network tab
> > - info and error messages in the JS Console tab
> >
> > Is there something that makes it still useful or we can drop it for
> Wicket
> > 8?
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
>
Re: Wicket Ajax debug window usefulness?
Posted by Tobias Soloschenko <to...@googlemail.com>.
Hi,
please don't drop it because of focus requests and some other debug information of actions requested on server side - server actions can't be logged at client side, but with the debug window.
kind regards
Tobias
> Am 17.04.2015 um 22:54 schrieb Martin Grigorov <mg...@apache.org>:
>
> Hi,
>
> Do you still use Wicket Ajax Debug window for something when developing
> your applications?
>
> I haven't used it in few years now and it seems I don't miss it.
> I can see all the debug information in the browser's dev tools:
> - ajax response in the Network tab
> - info and error messages in the JS Console tab
>
> Is there something that makes it still useful or we can drop it for Wicket
> 8?
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov