[
https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647802#action_12647802
]
Bruno Busco commented on OFBIZ-1999:
------------------------------------
Hi Hans,
many thanks for your review.
1. What do you mean for "it can take some time before the css is recognized
that comes with this change" ?
The changes to the main.css included in the patch defines new rules to be used
when rendering the manage portal toolbar and the portlet editing sreens.
2. I will check on the reported error.
3. The dashboard button has been included in the CommonAppBarMenu in the
CommonMenus.xml so it is automatically included and shown in all applications
that extends their AppBarMenu form the CommonAppBarMenu. Actually this is done
by several applications but not all of them. All the application that do not
extend from CommonAppBarMenu should be updated to comply with the new model
(but this is another issue).
The idea of the dashboard and the portal/portlet is the same as implemented in
JIRA (you can check it using your account on the OFBiz jira system).
Basically the framework itself offers a system where all application can
"register" a portlet without knowing who and where the porlet will be placed.
Every user can "build" its own dashboard selecting the desired portlets between
all the available portlets in its installation. Of course the list of the
available portlets will depend on the installed components.
Every porlet can be customized setting the portlets attributes.
In my idea the dashborad could be used in place of the MyPage component in this
way:
Instead of having the "MyPage" tab the user should use the "Dashboard" button.
This will take the user to a default dashboard. Then he can cusomize his
dashboard adding or removing portlets. This will replace what is actually done
accessing the "preference" tab of the MyPage application.
The screens that MyPage actually offers taking from the projectmgr application
should be defined as portlet by the projectmgr application itself and will be
automatically available in the portlet catalog.
The screens that MyPage actually offers and defines should rather be defined as
portlets in a "headless" MyPage component and the portlet system will render
them to the user.
For what concerning the authorizations, the idea is that the application that
defines the portlet is responsible for checking the permission in the portlet
itself. May be some more improvement could be done to the portlet system so
that the portlet is not even shown in the portlet catalog if the user has no
permission but this will be a refinement that we could do once we agree on the
opportunity of using this system and possibly after an initial commit so that
more contribution can be collected by the community.
Thank you again for the interest and comments.
> 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, 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.
