[jira] Created: (OFBIZ-1999) A portal/portlet implementation

[Nicolas Malin (Jira)]

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

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

David, Hans,
I think we are almost on the same page but not 100%. I want to clarify to points (very fastly, no time right now).

David,
My comments #1 was about the portletPAGE creation, not about the adding of a new portlet in a page that works ok.
In my original patch, accessing, to the ManagePortals screen it was possible to have a list of the user available PortalPAGES and the user could put a new name and a new description in the two text field, then press "Create" button and this added a new empty portalPAGE. Then, as the user has more that a PAGE, a combo box appears on the Dashboard bar (on the left) and the desired PAGE can be selected to be shown.

Then new portlets can be added to the newly created page.

Now this function does not work because the columns are not created totgether with the page and this is ALL we need to have the multi-page dashboard working.

Hans,
I am OK with your idea apart of having tha MyPortal component to deal with the PAGE creation. This is a feature embedded in the dashboard system itself and do not need to be implemented again (but only fixed to work again).

I will be able to give a look to your patch may be tomorrow, sorry.

> 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
>            Assignee: David E. Jones
>            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, 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.

[Nicolas Malin (Jira)]

     [ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruno Busco updated OFBIZ-1999:
-------------------------------

    Attachment: portalPageCreateColumnWithPage.patch

David, Hans,
please find attached the portalPageCreateColumnWithPage.patch that now creates one column when a new page is created.

David,
I have found and removed a little bug that caused that the list of user's available pages (portalPages) was not correctly set. This was why the drop-down to select about available user's pages and the "move portlet to page..." was not shown.

About the PageColumn services I will soon add the "addColumnToPortalPage" service. This is what we really need more than the "createPortalColumn". I think it will not be a auto but a simple service because the column needs to be linked to the existing Page.

Hans,
about the separation of the header with the page editing commands. I am quite OK with you but may be it is better to wait until we introduce the permission to edit a Page.
It a user has no Permission to edit a Page but only to view it, than the editing controls will not be shown (#if in the portalPage.ftl).
In any case, I think the header will still be usefull to show the page name and the drop-down do switch to a different page.

> 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
>            Assignee: David E. Jones
>            Priority: Minor
>         Attachments: portalPage-configure-off.jpg, portalPage-configure-on.jpg, portalPageCreateColumnWithPage.patch, portalPageImages.zip, portalPages.patch, portalPages.patch, portalPages.patch, portalPages.patch, 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.

[Nicolas Malin (Jira)]

     [ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruno Busco updated OFBIZ-1999:
-------------------------------

    Attachment: portalPageAddDeleteColumn.patch

In the new portalPageAddDeleteColumn.patch there are the following improvements:

1) When a new page is created a new column is also added by default (this was also in the previous portalPageCreateColumnWithPage.patch that I will remove to avoid confusion)

2) When a portlet is removed from a portalPageColumn all related attributes are also deleted from the database

3) When in configure ON mode a new "Add column" button is present in the dashboard page header

4) When in configure ON mode a new "Delete" button is present on each column

5) The "Add a portlet" has been moved from the page header to the column header so that the new portlet is already placed in the desired column

6) A delete button has been adde in the Manage Portal Page screen so that now the pages can be deleted

Still to do:
a) Column size setting. Has anybody know if an ajax drag can be used to set the column width?
b) Permissions
c) Dashboard pages sharing

> 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
>            Assignee: David E. Jones
>            Priority: Minor
>         Attachments: portalPage-configure-off.jpg, portalPage-configure-on.jpg, portalPageAddDeleteColumn.patch, portalPageImages.zip, portalPages.patch, portalPages.patch, portalPages.patch, portalPages.patch, 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.

[Nicolas Malin (Jira)]

     [ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruno Busco updated OFBIZ-1999:
-------------------------------

    Attachment:     (was: portalPageCreateColumnWithPage.patch)

> 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
>            Assignee: David E. Jones
>            Priority: Minor
>         Attachments: portalPage-configure-off.jpg, portalPage-configure-on.jpg, portalPageAddDeleteColumn.patch, portalPageImages.zip, portalPages.patch, portalPages.patch, portalPages.patch, portalPages.patch, 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.

[Nicolas Malin (Jira)]

     [ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruno Busco updated OFBIZ-1999:
-------------------------------

    Attachment:     (was: portalPageAddDeleteColumn.patch)

> 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
>            Assignee: David E. Jones
>            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, 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.

[Nicolas Malin (Jira)]

     [ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruno Busco closed OFBIZ-1999.
------------------------------

    Resolution: Fixed

As suggested this work can be considered closed.
Improvements are in OFBIZ-2057

> 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
>            Assignee: David E. Jones
>            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, 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.