[
https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648890#action_12648890
]
David E. Jones commented on OFBIZ-1999:
---------------------------------------
Thanks for your feedback and continued effort on this Bruno.
#1: I did test adding a portlet to a page and it worked, even though the
columnSeqId is not set (yes, that needs to be added to the UI); to make the
rendering work I changed it so the first column includes all portlets that are
not assigned to any particular column
#2: for the portal page we do need something in the config UI to
add/edit/remove columns, so yeah, on the configuration ON mode it would be
great to have stuff at the top to adjust column widths, add new columns, and
remove existing columns (the service that does this should remove all portlets
from a column before removing the column)
#3: yes, I think that would be good; I moved all of the data so far to be demo
data because they aren't really "real" portlets; but yes, if we add portlets
that are available OOTB then that would be cool; one thing to consider before
diving into that though would be to do the security service thing that we
briefly talked about so that users can only see portlets they have permission
for; here are my old notes about that: "NOTE: each screen used in a portlet
should be responsible for it's own permissions. May want to add something to
the UI for adding portlets to a portal page that somehow checks permissions on
available pages to not show the ones not available to the user. Could be done
by always using a permission service instead of direct permission checking in
screen actions, and then add the permissionServiceName to the PortalPortlet
entity."
> 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.
