Just develop the components separately. Or if you really need to debug (during integration testing) than you can just debug the generated code. It's not that complicated, if you look through the generated code a few times it will start to make sense.
Source maps can create their own issues. It's better to look at the actual code being executed instead of source maps. But my advice: don't write the code that calls jQuery in Python. It'll be a pain in many more ways than just debugging. Either go full python or if you're using js libs than use them from js. You can communicate between the python and js world using a DOM element. This will let you unit test each side of the components and let you debug natively. - lex On Mar 13, 2014 10:37 AM, "Hauke Duden" <hauke.du...@gmail.com> wrote: > We are using Python tools (also PyCharm, by the way). But the problem is > that this only allows us to debug the part of the software that is pure > Python. But as soon as third party Javascript libraries are involved > (jQuery UI, etc) then we cannot debug in a pure Python environment anymore. > This kind of code obviously requires a proper Javascript and DOM > environment to run these third party JS libraries. > > That is why I asked wether source maps are supported. If they are then we > could debug the UI stuff in Google Chrome or Firefox. That would be fine > for our purposes. But we really need *some* way to do step-by-step > debugging (also for our UI stuff). > > Hauke > > On Thursday, March 13, 2014 3:26:28 PM UTC+1, Lex Berezhny wrote: >> >> I develop, debug and test the app in python using Python tools (PyCharm >> in my case). >> >> If you are not using python tools then why the heck are you using pyjs? >> >> There are much better solutions if you prefer debugging in browser such >> as CoffeeScript and many other "js preprocessors". >> >> - lex >> On Mar 13, 2014 10:21 AM, "Adrien" <soul...@mailoo.org> wrote: >> >>> Hi, >>> >>> On 03/13/2014 10:04 AM, Hauke Duden wrote: >>> >>>> How are people debugging pyjs apps right now? >>>> >>> >>> I debug with the Firefox web console only, adding some "print" >>> statements here and there until I manage to find the bug. This may sound >>> ridiculous but Venkman, the Javascript (step by step) debugger which is >>> recommended for development with Firefox [1], was running so slow that it >>> was not usable at all. >>> >>> I don't know what other way you have to debug pyjamas applications... so >>> for myself, that's it: Python code live analyser (Pylint) and Firefox web >>> console. >>> >>> I would be interested as well to know about other's experiences. >>> >>> [1] http://pyj.be/#Developing >>> >>> Cheers, >>> Adrien >>> >>> -- >>> >>> --- You received this message because you are subscribed to the Google >>> Groups "Pyjs.org Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to pyjs-users+...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > > --- > You received this message because you are subscribed to the Google Groups > "Pyjs.org Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pyjs-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "Pyjs.org Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to pyjs-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
