OFBiz › OFBiz - Dev

[jira] Created: (OFBIZ-1999) A portal/portlet implementation

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

66 messages Options

1234

Nicolas Malin (Jira)

[jira] Updated: (OFBIZ-1999) A portal/portlet implementation

[ 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

OK now the portal/portlet implementation is complete (IMO).

Portlets can have as many attributes as required.
Please could you proceed with review and possiblty commit?

Thank you,
Bruno

> 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647532#action_12647532 ]

Hans Bakker commented on OFBIZ-1999:
------------------------------------

Hi Bruno,

I had a look at this.
1. for other people who look at this, it can take some time before the css is recognized that comes with this change.
2. A small error: the attributes are initially not defined so the attributeMap OUT parameter should be optional:
<attribute name="attributeMap" type="Map" mode="OUT" optional="true"/>
3. The dashboad button is only available in the project manager.

Although this looks promising i have to think about how to use this in the mypage component. Every other component can define portal pages but we want to be sure that these page can only be selected/used if the correct security permission is in place. A customer should see different pages than that an employee should see.

Hans

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ 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.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647805#action_12647805 ]

Jacques Le Roux commented on OFBIZ-1999:
----------------------------------------

Quick comment, I guess the css issue is only a browser cache issue. From my experience, most of the time a page actualisation is enough but sometimes you need to empty the cache to take into account the new CSS definitions.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647813#action_12647813 ]

Jacques Le Roux commented on OFBIZ-1999:
----------------------------------------

Bruno,

I did not test yet but from your point 3 explanation it looks promising.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647824#action_12647824 ]

Bruno Busco commented on OFBIZ-1999:
------------------------------------

Jacques,
yes I hope so.
I am thinking more and more that a Confluence page that explains the system and how to use it would be beneficial.
I would like to do as Midrul as done here: http://docs.ofbiz.org/display/OFBIZ/Enhancing+Display+Widget+to+use+Ajax.InPlaceEditor
WDYT?

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647826#action_12647826 ]

Jacques Le Roux commented on OFBIZ-1999:
----------------------------------------

Yes sure it will be easier to find than here.

The only problem we have with Confluence, as we use it, is organisation.
Too few people (to say the least) are trying to better organize things in the Wiki.
This is something we really miss in OFBiz (If you compare with other Apache projects, without comparing with commercials)
Maybe it's because this part is not still mature though.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647941#action_12647941 ]

Bruno Busco commented on OFBIZ-1999:
------------------------------------

Yes,
things in Confluence are definitively not so easy to find.
Could this be an additional reason to try to move faster on using OFBiz itself (the CMS) to keep all documentation?

BTW in order to have a clear idea of what the PortelPortlet patch adds to OFBiz, please refer to this page of the JIRA documentation:
http://www.atlassian.com/software/jira/docs/latest/dashboard.html

The patch implements the same feature in OFBiz.
It's a pity that people seems not interested in including this feature into OFBiz.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ 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.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647971#action_12647971 ]

Jacques Le Roux commented on OFBIZ-1999:
----------------------------------------

Bruno,

About portlet, for instance did you see Anil's comment in r717986 ?

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicolas Malin (Jira)

[jira] Assigned: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David E. Jones reassigned OFBIZ-1999:
-------------------------------------

Assignee: David E. Jones

> 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647977#action_12647977 ]

David E. Jones commented on OFBIZ-1999:
---------------------------------------

I apologize for the delay on this Bruno. I do actually intend to review and commit this patch in the near future (today if travel and such is not too time consuming), and would have done it sooner but wanted to spend my spare hours on some follow up from the conference (ie the big emails I've been sending out about this and that).

> 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647992#action_12647992 ]

Bruno Busco commented on OFBIZ-1999:
------------------------------------

Thank you guys,
I did not intend to be pushing on this, only thinking that a review is needed since I am not sure that all the stuff is done in the best way.

> 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648072#action_12648072 ]

David E. Jones commented on OFBIZ-1999:
---------------------------------------

Just an FYI, I'm working on this now... so "taking the token" as it were.

There are a few changes/cleanups I'm working on, and hopefully I'll finish them tonight but please wait until I'm finished.

I'll commit everything so far, and then (especially Bruno) if you have other changes you can send additional patches (until we get tired of reviewing and committing your patches and invite you to be a committer, of course... ;) ).

> 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648106#action_12648106 ]

David E. Jones commented on OFBIZ-1999:
---------------------------------------

The bulk of this is now in SVN, rev 718185. Please see comments on that commit.

Bruno: I made various changes and cleanups and filled in a few holes, please see my commit comments for details. Thanks for your work on this, it's really pretty neat and opens up a lot of options for future improvements.

For all watching: please test and give feedback. If things look okay we can close this issue and open other issues for enhancements to it.

> 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648353#action_12648353 ]

Bruno Busco commented on OFBIZ-1999:
------------------------------------

Wow!
Thank you David,
I have seen your changes and I must apologize to have pushed. I understand that it took a lot of work from your side also.

BTW, a couple of comments.

1) Having introduced the PortalColumn is greate but now there is a problem when the user adds a new PortalPage. No portlet can be added to the new PortalPage because no Column is created along with the PortalPage.

2) How the user should change the column sizes? Are we ok if we show, while in configuration ON mode, a combo box or something in the column header to set the column width?

3) Can we thing to a number of PortalPortlets defined in the framework itself? I mean, for instance the login portlet could it be a system defined portlet and not only a demo portlet?

> 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648365#action_12648365 ]

Bruno Busco commented on OFBIZ-1999:
------------------------------------

Could we think to have some controls to set the number of columns of a page and their sizes in the ManagePortalPage? https://localhost:8443/example/control/ManagePortalPages

> 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648898#action_12648898 ]

Hans Bakker commented on OFBIZ-1999:
------------------------------------

Hi Bruno, David,

This looks very good, an excellent extension of the frame work.
One problem i found however when a new portalpage is added and then a new portlet is added to it.... It does not show in the configuration screen. When the CreatePortalPage service is changed to add also the columnSeqId then it works.....

+ <make-value entity-name="PortalPageColumn" value-name="newEntity1"/>
+ <set-pk-fields map-name="parameters" value-name="newEntity1"/>
+ <make-next-seq-id value-name="newEntity1" seq-field-name="columnSeqId"/>
+ <create-value value-name="newEntity1"/>

In the config screen (portalPage.ftl) it would be nice to separate the header and the actual screen so a portal page can be shown without the ability to configure it and it looks like any other screen.

Exiting stuff, can't wait to actually use it in MyPage!
Hans

> 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.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-1999) A portal/portlet implementation

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648899#action_12648899 ]

David E. Jones commented on OFBIZ-1999:
---------------------------------------

Actually, there are no CrUD service for PortalPageColumn, so those need to be created and the code snippet in the message from Hans should go in the createPortalPageColumn service (or better just use the auto-entity stuff).

> 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.

1234