[MAGNOLIA-364] Customable Dialogs Created: 02/May/05  Updated: 17/Mar/09  Resolved: 06/May/05

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 2.1 Final

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   
  • you can define a class in the dialog-definition
  • Template Pattern: OnCreate, OnSave, OnPostSave, OnPreSave

Since i still use the ugly Save Control i will not add other things we talked about: validating, ...)



 Comments   
Comment by Philipp Bracher [ 04/May/05 ]

during the modification i will move cms.gui.dialogs.pages to module.admininterface.dialogs

This is more natural i think

Comment by Philipp Bracher [ 04/May/05 ]

commited the following:

  • Refactored the SimlpeDialogBasePage to a MVCServlet
  • Created a DialogMVCHandler for common dialog handling
  • Created DialogMVCHandler subclassed for the ParagraphEditDialog and ParagraphSelectDialog (was inside the SimlpeDialogBasePage)
  • moved cms.gui.dialog.pages to module.admininterface.pages /dialogs depending on what it is

One can easily subclass the DialogMVCHandler (or subclasses) to build customized dialogs.

see javadoc for details.

todo:

  • adappt the DialogMVCServlet.getHandler() so that it gets the class for instantiation from the
    configuration (optional class attribute in dialog definition) .
  • moving the DialogPages for roles and users to DialogHandler (pages/* to dialogs/*)
Comment by Philipp Bracher [ 06/May/05 ]

commited the following:

  • dialogs can have a class property
  • dialogs can be defined inside adminInterface/Config
  • The runtime can register dialogs at any time
  • move the user and role dialog to the new model
  • onPreSave, onSave, onPostSave
  • dialogx/<dialogname>.html maps to the registered dialog

This means: you can customize saving and loading of the dialogs (also paragraph dialogs)

This were the first basic steps. I will not change to mutch in the nearer future (until released 2.1)

Comment by Philipp Bracher [ 06/May/05 ]

I will add new task later.

Generated at Mon Feb 12 03:16:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.