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 < tobiassolosche...@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 <mgrigo...@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 >
