MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 9 · Fragments, components and reuse

When to make one

Lesson 93 of 176 · 3 min

THE THIRD TIME, NOT THE FIRST. Premature reuse produces A SHAPE THAT FITS NOTHING PROPERLY. The instinct on seeing something twice is to extract it. Waiting for the third is the difference between a fragment that helps and one everybody works around. THE REASON IS THAT TWO EXAMPLES CANNOT TELL YOU WHAT VARIES. Two customer panels look identical, so you extract exactly what they have in common — and the third turns out to need one extra field, a different action, and no header. Now the fragment has three parameters bolted on to accommodate a case it was not designed around, and each is a condition inside it. THREE EXAMPLES SHOW YOU THE AXIS OF VARIATION, WHICH IS THE THING WORTH DESIGNING AROUND. With three you can see what genuinely differs from case to case, and the fragment's parameters describe that rather than patching it. AND DUPLICATION IS CHEAPER THAN

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.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 9 · Fragments, components and reuse

  1. 1The component library you already have
  2. 2Fragments: a piece of page you reuse
  3. 3When to make one
  4. 4Custom components
  5. 5Sharing across applications
  6. 6Theming and staying consistent
  7. 7What breaks: two reuse failures
  8. 8Lab briefing · Extract a fragment properly
When to make one — Oracle Visual Builder: Applications That Outlive Their First Release — MSAMM