Ir al contenido
Todas las pláticas
  • Odoo Experience 2020
  • Charlas
  • Expositores
  • Agenda
  • Todos los eventos
  • Odoo Experience 2020
  • Todas las pláticas
 
  • Odoo Experience 2020
  • Charlas
  • Expositores
  • Agenda


  • Charlas
  • Keynote - Vision & Strategy
    Fabien Pinckaers
    Hecho
  • Opening Keynote - Unveiling Odoo 14
    Fabien Pinckaers
    Hecho
  • UX in Business Apps: a Workshop for App Developers
    Fabien Pinckaers
    Hecho
  • Best Tools for First-Time Odoo Development
    Yannick Tivisse
    Hecho
  • Owl: The New Odoo UI Framework
    Géry Debongnie
    Hecho
  • Odoo Website: How to Develop Building Blocks
    Samuel Degueldre
    Hecho
  • Developing New Widgets for Your Views in Owl
    Géry Debongnie
    Hecho
  • The Right Way to Develop Website & eCommerce Features
    Jérémy Kersten
    Hecho
  • Tutorial: Develop an App with the Odoo Framework
    Yannick Tivisse
    Hecho
  • An In-depth Journey into Odoo's ORM
    Raphael Collet
    Hecho
Cargando vídeo...
Why Browser Debugger is a Developer's Best Friend
Developer Talk
Ubicación: Studio 5 - 1/10/20, 15:00 - 1/10/20, 15:30 (Europe/Brussels) (30 minutos)
Haga la prueba
Why Browser Debugger is a Developer's Best Friend
Loan Sens
Investigation Developer at Odoo
Loan Sens
Investigation Developer at Odoo

Loan is a member of the Technical Support team at Odoo S.A. in Belgium. After graduating with a Master in Computer Science, he joined Odoo in 2019. In this role, he is responsible for investigating support tickets that clients submit. His specialties are issues related to Website and Web Client/Javascript.


Odoo's logs, tracebacks, and breakpoints in the code are all useful to understand how Odoo works. However, your browser can also be a precious ally!

In this talk, we will cover some of the developer tools available in your browser. We will see how interactions with the server work and how that is valuable information for custom developments, debugging/troubleshooting, and to spot performance issues.

Join us!

Cuestionario

What is the point of using "debug=assets" mode ?
Being able to see the real HTML code of our webpage. Without it some features are hidden such as menus and some fields. Use assets source file in order to see the actual code that is ran. Otherwise we could have the minified version which harder to read. Use to troubleshoot performance issue in order to load all ressources that are usually stored in the cache. Without it, cache resource may be use which may miss our modifications
What is the purpose of the "Network" development tool?
See request/call done between the page and the server See the HTML code of the currently loaded page Execute JavaScript code and evaluate in-scope variable values (if code is paused by a breakpoint in "Source")
I would like to know what happen in Odoo's code when I click on the "Setting" App on the Home page. I don't have any access to the server code/logs and there is no tooltip message to inform me on the method call. What would be the MOST EFFECTIVE way to see what method is called?
Open the "Elements" tool and read the HTML code of the button. The method called is defined on it Open the "Source" tool. Search for the JavaScript code trigger when the button is pressed. Add a breakpoint. Click the button. Evaluate in the "Console" the in scope variables until finding the one responsible for that. Open the "Network" tool. Click the button. Choose the first created requests and look at its "Request Payload"
Entradas
Lista de precios: US: North America Lista de precios
US: North America

Odoo Experience on YouTube

1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.

Live support on Youtube
Watch now