Magnolia

Ability to choose a custom save handler per control/field

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.6 RC1
  • Fix Version/s: 3.6.1
  • Component/s: admininterface, core, gui
  • Labels:
  • Description:
    Hide

    We know that the current SaveHandlerImpl is a big limit in creating customized controls and behaviours (for example it could be needed to create an image and save it into the repo from a configured text).

    SaveHandlerImpl could easily be expanded in order to allow the configuration of custom save handles per dialog fields (without breaking or requiring any api change). I'd like to commit this contribution (already done) for 3.6

    Show
    We know that the current SaveHandlerImpl is a big limit in creating customized controls and behaviours (for example it could be needed to create an image and save it into the repo from a configured text). SaveHandlerImpl could easily be expanded in order to allow the configuration of custom save handles per dialog fields (without breaking or requiring any api change). I'd like to commit this contribution (already done) for 3.6

Issue Links

Activity

Hide
Fabrizio Giustina added a comment - 17/Jul/08 9:08 PM

committed to trunk (3.6.1), you can now choose a specific save handler by adding the fully qualified class name of a class implementing the CustomSaveHandler interface in the property "saveHandler" in a field

Show
Fabrizio Giustina added a comment - 17/Jul/08 9:08 PM committed to trunk (3.6.1), you can now choose a specific save handler by adding the fully qualified class name of a class implementing the CustomSaveHandler interface in the property "saveHandler" in a field

People

Dates

  • Created:
    16/Jul/08 9:47 PM
    Updated:
    01/Oct/08 3:14 PM
    Resolved:
    17/Jul/08 9:08 PM