Oracle Visual Builder: Applications That Outlive Their First Release · Module 2 · The workspace and your first app
The browser tools are your real debugger
Lesson 20 of 176 · 3 min
Network tab, console and the framework's own logging. THE SINGLE SKILL THAT MAKES EVERYTHING AFTER THIS MODULE DIAGNOSABLE. Module 1 Lesson 1 said the designer hides what is happening; the browser tools are where it is visible, and this is the most important lesson in the first half of this course. THE NETWORK TAB IS THE ONE THAT MATTERS MOST, BECAUSE ALMOST EVERY FAILURE IN THIS COURSE IS A REQUEST. It shows what was sent, where, with what headers, and what came back — status, body, timing. An empty table on a page is one of four things, and the network tab distinguishes all four in ten seconds: the request was never made, it was made and refused, it succeeded and returned nothing, or it succeeded and the data did not reach the component. THAT LAST DISTINCTION IS THE ONE THE DESIGNER CANNOT HELP WITH AT ALL. A service returning…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.
In this module: Module 2 · The workspace and your first app
- 1The designer, and the four places you will live
- 2Applications, flows and pages
- 3Your first application, start to finish
- 4Preview, and what it is not
- 5The visual designer and the code behind it
- 6Naming, and why it matters more than it should
- 7The browser tools are your real debugger
- 8What breaks: the first-week mistakes
- 9Lab briefing · Build it, run it, break it