[
https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Busco updated OFBIZ-1999:
-------------------------------
Attachment: portalPages.patch
More improvements in the new attached patch:
- Added services to move portalPortlets around in the portalPage
- Added services to move portalPortlets in a different portalPage
- Added services to create and update portalPages
- Added ManagePortal Screen to edit name/description of the portalPage and to
create new portalPage
- Aligned portlets vertically in the portalPage
- Used a drop-down to switch between the available portalPages
Still to implement:
- Permission check
- Better LOGIN portlet (this should switch automatically between
username/password request and user info/preferences if we are logged in or not)
- Better MYPAGE portlets
- CSS
- Portlet configuration by means of an associated form
- New Screen Widget "widget element": include-portal-page, attributes:
portalPageId
Thank you for any hint / comment / review
> 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: portalPages.patch, portalPages.patch, portalPages.patch,
> 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.
