I would say Ecipse+pydev for web2py, and firebug for the javascript. This is how I debug all of my ajax apps that don't work quite right. You can set breakpoints in firebug and iterate over them to understand what the javascript is working with. If you are using debugging in pydev, when your ajax call requests from the server, if you have a breakpoint set it will trip and you can switch over to step through code as well.
Another thing I will do, is when I am designing a controller function to accept an ajax input, I will spoof the values during testing and using generic views. dbid = request.args(0) or request.vars.dbid or 123 # default to testing sample value = request.args(1) or request.vars.value or "Hello World" # default to testing sample # do some operations on values return (dbid, value) This way I know the controller works without a doubt, then I just remove the defaults, and then create my ajax call, and debug it. -Thadeus On Tue, Oct 20, 2009 at 10:17 AM, weheh <[email protected]> wrote: > > Issue is resolved, but would still like to hear user thoughts about > what is best environment for debugging ajax scripts. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
