portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Woonsan Ko (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] [Commented] (JS2-1232) Portlet Instances
Date Thu, 12 May 2011 03:11:47 GMT

    [ https://issues.apache.org/jira/browse/JS2-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032241#comment-13032241
] 

Woonsan Ko commented on JS2-1232:
---------------------------------

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

> Portlet Instances
> -----------------
>
>                 Key: JS2-1232
>                 URL: https://issues.apache.org/jira/browse/JS2-1232
>             Project: Jetspeed 2
>          Issue Type: New Feature
>          Components: Portlet Registry
>    Affects Versions: 2.2.2
>            Reporter: David Sean Taylor
>            Assignee: David Sean Taylor
>             Fix For: 2.2.2
>
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message