Forrest
  1. Forrest
  2. FOR-970

Add a way to have plugin specific resources, such as its own CSS styling, independent of skin or theme

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 0.7, 0.8
    • Fix Version/s: 0.10-dev
    • Labels:
      None
    • Urgency:
      Normal

      Description

      It would be nice if plugins could be a little more independent of core skins and themes for plugin specific styling.
      This could be CSS, or something else, I have only identified CSS needs at present.

        Issue Links

          Activity

          Gavin created issue -
          Gavin made changes -
          Field Original Value New Value
          Link This issue blocks FOR-412 [ FOR-412 ]
          Hide
          Ross Gardler added a comment -
          Can you provide a use case for this. When would a plugin be used independently of skins/themes?

          As things stand at present plugins can provide CSS class attributes for generated elements. These classes can then be defined in skincon.xml (for skins) or in the theme definition in themes. Can you describe why this doesn't work out for your use case.
          Show
          Ross Gardler added a comment - Can you provide a use case for this. When would a plugin be used independently of skins/themes? As things stand at present plugins can provide CSS class attributes for generated elements. These classes can then be defined in skincon.xml (for skins) or in the theme definition in themes. Can you describe why this doesn't work out for your use case.
          Gavin made changes -
          Link This issue is blocked by FOR-971 [ FOR-971 ]
          Gavin made changes -
          Link This issue is blocked by FOR-971 [ FOR-971 ]
          Gavin made changes -
          Link This issue blocks FOR-971 [ FOR-971 ]
          Hide
          Ross Gardler added a comment -
          I see the use cases now Gavin (via the linked issues) - thanks.
          Show
          Ross Gardler added a comment - I see the use cases now Gavin (via the linked issues) - thanks.
          Hide
          Ross Gardler added a comment -
          I had the same need when I built the ecs input plugin (in whiteboard). The index.xml page describes what I did (basically defined the available CSS and expected the user to provide their own CSS). I opted for this because, since we don't know the users skin/theme we can't really provide meaningful default CSS.

          However, I see some defaults may be useful.

          My initial thought is that the plugins could provide an "extra.css" or "extra-css.xml" file. These can then be collated when the plugin is installed at startup. The collated document is then embedded in skinconf.xml or a dispatcher contract as appropriate.
          Show
          Ross Gardler added a comment - I had the same need when I built the ecs input plugin (in whiteboard). The index.xml page describes what I did (basically defined the available CSS and expected the user to provide their own CSS). I opted for this because, since we don't know the users skin/theme we can't really provide meaningful default CSS. However, I see some defaults may be useful. My initial thought is that the plugins could provide an "extra.css" or "extra-css.xml" file. These can then be collated when the plugin is installed at startup. The collated document is then embedded in skinconf.xml or a dispatcher contract as appropriate.
          Thorsten Scherler made changes -
          Link This issue incorporates FOR-635 [ FOR-635 ]
          Hide
          Thorsten Scherler added a comment -
          I think the image should come from something like FOR-970
          Show
          Thorsten Scherler added a comment - I think the image should come from something like FOR-970
          Tim Williams made changes -
          Fix Version/s 0.10 [ 12310092 ]
          Fix Version/s 0.9-dev [ 12310041 ]
          Gavin made changes -
          Link This issue blocks FOR-412 [ FOR-412 ]
          Gavin made changes -
          Link This issue is depended upon by FOR-412 [ FOR-412 ]
          Gavin made changes -
          Link This issue blocks FOR-971 [ FOR-971 ]
          Gavin made changes -
          Link This issue is depended upon by FOR-971 [ FOR-971 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              Gavin
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development