[MGNLUI-3263] Revise and generalise Page editor extensions Created: 18/Nov/14  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.4
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Espen Jervidalo Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLUI-3234 Allow additional components in workbe... Closed
is depended upon by MGNLUI-3148 Extract pages app and editor to prope... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

The extension concept used for page- and statusBar in the page editor should be generalized so at least the essential APIs can be reused inside the workbench for controls e.g. for switching dam providers.

Some tasks:

  • extraction out of pages module into e.g. framework, content-app ..
  • rename "Extension" classes


 Comments   
Comment by Mikaël Geljić [ 05/Jun/15 ]

Guess we could briefly review some naming while we're at it:

  • Especially for definitions, still not much convinced by ContentTool, and it's gonna be harder to change afterwards (will require upgrades)
  • Simplify QueryStatementChangedEvent.
Generated at Mon Feb 12 09:04:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.