[
https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647968#action_12647968
]
Jacques Le Roux commented on OFBIZ-1999:
----------------------------------------
Note that this is not an intrinsic Confluence properties and that we would have
the same problem with OFBiz CMS. It's an organisationnal issue. David said in
dev ML that it's a rather difficult issue to deal with because we are not
always on the same mind. I think that it's not the real problem since we can
share our opinions and then if necessary make a vote.
The harder problem is to coordinate our work. Subversion allow us to coordinate
smoothly on most things. So I guess we should try to use the same tool for
documentation too. Maybe using the CMS component would be a solution, yes. BTW
we should have better discussed this on dev ML as there is a wider public there.
About the portlet, just be patient Bruno, I'm sure a lot of people are
interested by this issue, it's only that there are only 24h in a day ;) Hans
seems interested to use it in MyPage, just let him the time to think about it
and to come back to you.
> 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.
