[
https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640068#action_12640068
]
Bruno Busco commented on OFBIZ-1999:
------------------------------------
David,
I am really happy for the positive feedback and perfectly agree on your notes.
At the moment the implementation I attached was really draft but I preferred to
communicate the idea to the community becouse I think that the efforts we are
going to spend in orther to have the MyPage application more general could be
spent on the PagePortal stuff.
A PagePortal could then be used as users's MyPage.
An additional feature that I was thinking to add in the model at a later stage
was the PortalPortlet configuration. With this I mean that a PagePortlet
instance in a PagePortal could be configured in a different way from another
instance of the same PortalPortlet.
For instance a PortalPortlet that lists the last user communications can be
configured to show the last 10 or 20 communications and this is up to the user
that configures his PortalPage.
To to this I was thinking to add a "configureFormLocation" in the PortalPortlet
entity to link a form to the PortapPortlet. This will be used when the user
press the "edit" button on the PortalPortlet configuration bar. At the moment I
have no idea of how the configured parameters could be saved in the database
(in which entity) and passed to the PortalPortlet screen to affect the
rendering.
> 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: portal.zip, screenshot-1.jpg, screenshot-2.jpg
>
>
> 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.
