MSAMM
Back to course

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

What breaks: two reuse failures

Lesson 97 of 176 · 3 min

A FRAGMENT WITH SO MANY PARAMETERS IT WOULD HAVE BEEN SIMPLER TWICE, and A SHARED COMPONENT CHANGED UNDER THREE APPLICATIONS. THE OVER-PARAMETERISED FRAGMENT IS THE ONE THAT LOOKS LIKE GOOD ENGINEERING THE WHOLE TIME IT IS BEING BUILT. Extracted from two pages, then bent to fit a third, then a fourth — and each parameter was a reasonable response to a real requirement. Lesson 3, and at seven parameters, four of them booleans switching sections on and off, it is harder to read than the copies would have been. THE TELL IS THAT NOBODY CAN USE IT WITHOUT READING IT. A well-shaped fragment is placed and given the two things it needs; this one requires studying its internals to work out which combination of flags produces the layout you want. Which means it is not reuse — it is a shared thing everybody has to understand fully, which is the

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