[ 
https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642796#action_12642796
 ] 

Bruno Busco commented on OFBIZ-1999:
------------------------------------

Hans,
thank you for testing the patch.
The edit button is commented because the portlet parametrization is not yet 
implemented and not even designed.
The edit button should show a form that should be specified with the portlet 
screen. This form should be used to set some parameters that would specify how 
the portlet will be displayed.
For instance a project summary portlet could be parametrized with the 
particular project to be shown.

About the possibility for the user to configure their pages, I think it would 
be something similar to what the user does now in the MyPage preferences where 
all the checkboxes are available.
The difference is that the portal system is more general and will be extended 
as long as new portlet will be defined in the application components.



> A portal/portlet implementation
> -------------------------------
>
>                 Key: OFBIZ-1999
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1999
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: ALL COMPONENTS
>            Reporter: Bruno Busco
>            Priority: Minor
>         Attachments: portalPage-configure-off.jpg, 
> portalPage-configure-on.jpg, portalPageImages.zip, portalPages.patch, 
> portalPages.patch, portalPages.patch, portalPages.patch, portalPages.patch, 
> portalPages.patch, portalPages.patch
>
>
> Hi devs,
> I am trying to set up a portal/portlet model similar to what is implemented 
> into JIRA user interface.
> The Idea is that every component can "register" its selected screens as 
> system portlets using something like:
> <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" 
> screenPath="component://portal/widget/CommonScreens.xml#welcome" />
> In this case the portal component has registered a welcome screen as 
> "WELCOME" portlet.
> The portlets can later be "mounted" into portals with the entity:
>     <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME"      
> columnNum="1" sequenceNum="1" />
>     <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN"        
> columnNum="2" sequenceNum="2" />
>     <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001"   
> columnNum="1" sequenceNum="2" />
>     <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002"   
> columnNum="3" sequenceNum="2" />
>     <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003"   
> columnNum="1" sequenceNum="2" />
> In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and 
> PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and 
> with the indicated order.
> Every portal is defined by the entity:
> <Portal portalId="DEFAULT" name="Default home portal" description="The 
> default OFBiz portal" owner="admin" />
> And is related to a specific user. So every user can have as many portals he 
> needs and a DEFAULT portal can be defined by the admin.
> In the attached zip file there is a very draft implementation of this that I 
> would like so submit to your attention to share ideas about it and eventually 
> develop together.
> Many thanks for your feedbacks,
> Bruno

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to