Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-28061

As a developer, I want to easily integrate an OE button for a custom tag I have created

    Details

    • Type: Story Story
    • Status: Closed
    • Priority: High High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      The purpose of the story is to make it much easier for developers to add a button to the Online Editor that inserts a custom tag they have created.

      At the moment (1.11), adding a button requires changes to core files, as well as a subsantial javascript file, configuration and CSS. Once we have agreed on the UI for custom tags, it should be fairly easy to automate the addition of such a button.

      Given the name and properties of a custom tag, all buttons have the same behaviour. The icon and help text are specific to each tag.

      Open questions

      Unless I'm mistaken, there are client side tools to "theme" the OE, and enable a set of button or another. It would be more optimal, maybe, to use that feature to choose which buttons appear and where.

      In any case, it is important that a maintainer has full freedom about the buttons that show up.

      Even though it ain't limited to the buttons, autoconfiguration should be used as much as possible for those tags. For instance, the CSS or icon for a custom tag could be picked based on a standardized path (platform/oe/custom_tags for instance).

        Activity

        Bertrand Dunogier created issue -
        Bertrand Dunogier made changes -
        Field Original Value New Value
        Epic Link EZP-25357 [ 52851 ]
        Bertrand Dunogier made changes -
        Status Backlog [ 10000 ] Specification [ 10002 ]
        Bertrand Dunogier made changes -
        Description The purpose of the story is to make it much easier for developers to add a button to the Online Editor that inserts a custom tag they have created.

        At the moment (1.11), adding a button requires changes to core files, as well as a subsantial javascript file, configuration and CSS. Once we have agreed on the UI for custom tags, it should be fairly easy to automate the addition of such a button.

        Given the name and properties of a custom tag, all buttons have the same behaviour. The icon and help text are specific to each tag.

        h3. Open questions

        Unless I'm mistaken, there are client side tools to "theme" the OE, and enable a set of button or another. It would be more optimal, maybe, to use that feature to choose which buttons appear and where.

        In any case, it is important that a maintainer has full freedom about the buttons that show up.

        Even though it ain't limited to the buttons, autoconfiguration should be used as much as possible for those tags. For instance, the CSS or icon for a custom tag could be picked based on a standardized path ({{platform/oe/custom_tags for instance}}).
        The purpose of the story is to make it much easier for developers to add a button to the Online Editor that inserts a custom tag they have created.

        At the moment (1.11), adding a button requires changes to core files, as well as a subsantial javascript file, configuration and CSS. Once we have agreed on the UI for custom tags, it should be fairly easy to automate the addition of such a button.

        Given the name and properties of a custom tag, all buttons have the same behaviour. The icon and help text are specific to each tag.

        h3. Open questions

        Unless I'm mistaken, there are client side tools to "theme" the OE, and enable a set of button or another. It would be more optimal, maybe, to use that feature to choose which buttons appear and where.

        In any case, it is important that a maintainer has full freedom about the buttons that show up.

        Even though it ain't limited to the buttons, autoconfiguration should be used as much as possible for those tags. For instance, the CSS or icon for a custom tag could be picked based on a standardized path ({{platform/oe/custom_tags}} for instance).
        Bertrand Dunogier made changes -
        Status Specification [ 10002 ] Specification Done [ 10003 ]
        Assignee Bertrand Dunogier [ bertrand.dunogier@ez.no ]
        Bertrand Dunogier made changes -
        Status Specification Done [ 10003 ] Specification Review [ 10038 ]
        Bertrand Dunogier made changes -
        Status Specification Review [ 10038 ] Specification [ 10002 ]
        Bertrand Dunogier made changes -
        Status Specification [ 10002 ] Closed [ 6 ]
        Resolution Done [ 9 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Bertrand Dunogier
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: