Oracle Visual Builder: Applications That Outlive Their First Release · Module 2 · The workspace and your first app
The visual designer and the code behind it
Lesson 18 of 176 · 3 min
Every page is JSON YOU CAN READ. When to open it, when not to, and WHY KNOWING IT IS THERE CHANGES HOW YOU DEBUG. The designer is an editor over files, and those files are readable — which is a fact worth knowing long before you need to use it. WHY IT CHANGES HOW YOU DEBUG IS THE POINT OF THE LESSON. A visual tool makes it feel as though the application is a state of the designer — and it is not: it is a set of files describing pages, variables and chains. Once you hold that, a page behaving strangely is something you can INSPECT rather than something you have to coax the designer into revealing. WHEN TO OPEN IT: WHEN THE DESIGNER AND REALITY DISAGREE. A property you set that does not seem to apply, a binding you cannot find, a component behaving as though it has…
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