Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.2
    • Fix Version/s: 2.2.2
    • Component/s: Portlet Registry
    • Labels:
      None

      Description

      Instances allow site editors to quickly create new portlet variants based on modified preference and other descriptor settings.
      Use case: a customized IFrame portlet with all preferences and localized metadata pre-configured.

      • create portlet instances from a portlet (API)
      • wizard to create an instance from a portlet, overriding preferences
      • Integrate with search, toolbox
      • protect instances from deletion on deployment

      Further requirements from Ron Wheeler:

      • Portlet can be be created based on an existing portlet definition/template.
        -Portlet definitions include:
        • Name (not in template)
        • Title - could have a flag indicating if the title should be displayed in the title bar or not. (not in template)
        • Description (would be a general description in the template which would be the default for a new instance)
        • Class
        • Link to Documentation
        • icon for portlet catalog
        • collection of labels and values for the parameters.

      To create a new portlet from an existing template, the system admin would supply a new Name, Title, Description.
      The Class would be the key to finding the template and should be picked off a drop-down list.
      The template specifies the parameters that can be passed to the Class.

      Each parameter should have a flag that indicates whether the parameter is mandatory or optional.

      It would be nice to be able to specify a default value and a description of each parameter to help the system administrator understand what each parameter is( or could actually have documentation if anyone would read it).

      Once all this information is specified, the portlet would be available for inclusion in a page.

        Activity

        Hide
        David Sean Taylor added a comment -

        thanks

        Show
        David Sean Taylor added a comment - thanks
        Hide
        Woonsan Ko added a comment -

        Hi David,

        I fixed the cloning popup window's look&feel problem by: r1102160, r1102159.
        Basically, the requester should pass "_inheritdeco" request parameter if it wants to use that specified decorator for pages having "inherit" decorator.
        So, in portal pipeline, /decorations/layout/inherit/decorator-macros.vm does read this parameter to change the decorator (in inheritLayoutObjects macro.)
        Interestingly, the macro uses the default value, "jetspeed", if nothing is passed. Unlike this, jetui.jsp in /ui pipeline, does read the parameter but no default value.
        That was the reason of the differences.
        Therefore, I added "_inheritdeco" request parameter in toolbox.jsp.

        I'll resolve this issue now because this problem seems the last one for this issue.

        Regards,

        Woonsan

        Show
        Woonsan Ko added a comment - Hi David, I fixed the cloning popup window's look&feel problem by: r1102160, r1102159. Basically, the requester should pass "_inheritdeco" request parameter if it wants to use that specified decorator for pages having "inherit" decorator. So, in portal pipeline, /decorations/layout/inherit/decorator-macros.vm does read this parameter to change the decorator (in inheritLayoutObjects macro.) Interestingly, the macro uses the default value, "jetspeed", if nothing is passed. Unlike this, jetui.jsp in /ui pipeline, does read the parameter but no default value. That was the reason of the differences. Therefore, I added "_inheritdeco" request parameter in toolbox.jsp. I'll resolve this issue now because this problem seems the last one for this issue. Regards, Woonsan
        Hide
        David Sean Taylor added a comment -

        This issue is getting close to completion. I still need to solve one more problem reported by Woonsan:

        "The cloning popup window UI's look&feels are slightly different from each other between /portal and /ui pipeline. There's no problem from the perspective of functionality though.
        Under /portal pipeline, the look&feel is okay (btw, the system popup pages are inherit/inherit decoration).
        I think you once changed the /ui pipeline's decoration behaviors, so styles with 'inherit' doesn't seem to work. I have tried to fix this, but no success. Could you find a solution for that?"

        I will try...

        Show
        David Sean Taylor added a comment - This issue is getting close to completion. I still need to solve one more problem reported by Woonsan: "The cloning popup window UI's look&feels are slightly different from each other between /portal and /ui pipeline. There's no problem from the perspective of functionality though. Under /portal pipeline, the look&feel is okay (btw, the system popup pages are inherit/inherit decoration). I think you once changed the /ui pipeline's decoration behaviors, so styles with 'inherit' doesn't seem to work. I have tried to fix this, but no success. Could you find a solution for that?" I will try...

          People

          • Assignee:
            David Sean Taylor
            Reporter:
            David Sean Taylor
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Resolved:

              Development