On Mon, Apr 20, 2015 at 2:45 PM, Nick Pratt <nbpr...@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 <mgrigo...@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 <seb...@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 <s...@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 < > > > >> 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 > > > >>>> > > > >>> > > > > > > > > > >
