[jira] Created: (OFBIZ-1999) A portal/portlet implementation
Locked
1234
1234
[jira] Commented: (OFBIZ-1999) A portal/portlet implementation
 
|
[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640826#action_12640826 ] Bruno Busco commented on OFBIZ-1999: ------------------------------------ Thank you Hans, as you may have seen, in the patch I defined some portalPortlets in the MyPage component to have it available in the portalPages. However they are not working still very well (the MyTimesheet one does not work at all). It will be of great help if you could see what is wrong there and maybe redefine the MyPage portalPortlets in a correct way. Many thanks for your help. > 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, 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. |
[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=12640827#action_12640827 ] David E. Jones commented on OFBIZ-1999: --------------------------------------- I was thinking about the include-portal-page screen widget element and the primary key of the PortalPage entity. Right now there is just a portalPageId in the pk, so when a default page is overridden by a user a new portalPageId would have to be created, which would break the include-portal-page element that points to the original portalPageId. There is a "owner" field in the entity (might be more clear if it was called "ownerUserLoginId" instead) and we could add that to the pk (ie make it a pk field). When rendering a page with just a portalPageId we'd look for a record with the userLoginId of the current user and if that isn't found we'd use the "system" userLoginId or something. Does that make sense? > 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, 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. |
Re: [jira] Commented: (OFBIZ-1999) A portal/portlet implementation
|
|
Hi David,
in my original thought all the portalPages would have been rendered by a single "system" screen that would have offered to the logged in user all the portlaPages he has access to. This is what happens now accessing to the common/control/portalPage url. The portalPages available to the user to choose from should be the ones that belongs to the actual user plus all the portalPages defined as "public" (with a not yet present flag). I did not think to the portalPage overriding but only to the possibility for the user to create new pages. What you propose is a great solution to both have the portalPage overriding feature (even in the "system" portalPage rendering screen) and to have the include-portal-page screen widget element. Thank you! I will try to implement this. 2008/10/19 David E. Jones (JIRA) <[hidden email]> > > [ > https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640827#action_12640827] > > David E. Jones commented on OFBIZ-1999: > --------------------------------------- > > I was thinking about the include-portal-page screen widget element and the > primary key of the PortalPage entity. Right now there is just a portalPageId > in the pk, so when a default page is overridden by a user a new portalPageId > would have to be created, which would break the include-portal-page element > that points to the original portalPageId. > > There is a "owner" field in the entity (might be more clear if it was > called "ownerUserLoginId" instead) and we could add that to the pk (ie make > it a pk field). When rendering a page with just a portalPageId we'd look for > a record with the userLoginId of the current user and if that isn't found > we'd use the "system" userLoginId or something. > > Does that make sense? > > > 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, 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. > > |
[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=12640830#action_12640830 ] Bruno Busco commented on OFBIZ-1999: ------------------------------------ Hi David, in my original thought all the portalPages would have been rendered by a single "system" screen that would have offered to the logged in user all the portlaPages he has access to. This is what happens now accessing to the common/control/portalPage url. The portalPages available to the user to choose from should be the ones that belongs to the actual user plus all the portalPages defined as "public" (with a not yet present flag). I did not think to the portalPage overriding but only to the possibility for the user to create new pages. What you propose is a great solution to both have the portalPage overriding feature (even in the "system" portalPage rendering screen) and to have the include-portal-page screen widget element. Thank you! I will try to implement this. > 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, 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. |
[jira] Updated: (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 ] Bruno Busco updated OFBIZ-1999: ------------------------------- Attachment: portalPages.patch More improvements in the new attached patch: - New CSS styles and better layout (see new screenshots) - Changed "Portal" menu item to "Dashboard" and changed the logo link to it Still to do: - Handle more portalPortlets of the same kind in the same portalPage - Better handling of portalPortlet position change - Localization - Permissions > 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, 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. |
[jira] Updated: (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 ] Bruno Busco updated OFBIZ-1999: ------------------------------- Attachment: portalPage-configure-off.jpg > 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-off.jpg, portalPage-configure-on.jpg, 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. |
[jira] Updated: (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 ] Bruno Busco updated OFBIZ-1999: ------------------------------- Attachment: (was: portalPage-configure-on.jpg) > 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, 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. |
[jira] Updated: (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 ] Bruno Busco updated OFBIZ-1999: ------------------------------- Attachment: portalPage-configure-on.jpg > 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, 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. |
[jira] Updated: (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 ] Bruno Busco updated OFBIZ-1999: ------------------------------- Attachment: (was: portalPage-configure-off.jpg) > 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, 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. |
[jira] Updated: (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 ] Bruno Busco updated OFBIZ-1999: ------------------------------- Attachment: portalPageImages.zip portalPages.patch Hi, I prefer to attach an updated patch with the last I have done because I think I will not be able to work at it for the week, and just in case... Those are the improvements: - Added more CSS and icons for the portlet configuration (see new screenshot) - More portlets of the same kind can now live in the same portalPage - Rewritten the portalPage.ftl to have the portlet better displayed (it is now a table with only one row so that all portlets in a column are close and no row align is more present) Things still to do: - Permissions - Some weird behaviour while moving vertically the portlets - portlaPage overriding (as discussed in this thread) - Localization > 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 > > > 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. |
[jira] Updated: (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 ] Bruno Busco updated OFBIZ-1999: ------------------------------- Attachment: portalPage-configure-on.jpg > 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 > > > 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. |
[jira] Updated: (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 ] Bruno Busco updated OFBIZ-1999: ------------------------------- Attachment: (was: portalPage-configure-on.jpg) > 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 > > > 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. |
[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=12642550#action_12642550 ] Bruno Busco commented on OFBIZ-1999: ------------------------------------ Please consider that the portalPageImages.zip contains the new icons that should be unzipped in the image folder. > 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 > > > 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. |
[jira] Updated: (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 ] Bruno Busco updated OFBIZ-1999: ------------------------------- Attachment: portalPages.patch Hi, I have added localization to the patch. I think the patch is now ready to be reviewed and eventually committed. Many thanks, 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 > > > 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. |
[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=12642792#action_12642792 ] Hans Bakker commented on OFBIZ-1999: ------------------------------------ I had a look at it, the patch needs to be updated because it does not fit on the latest svn anymore. I think it is looking promising. Add a portal page does work, however the edit button, after adding it does not seem to do anything. although i doubt that a user will configure their pages, it could be created for the different functions in the company. I support committing this addition if the edit function works....i will have a look if it can be used in the mypage application. > 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 > > > 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. |
[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=12642796#action_12642796 ] Bruno Busco commented on OFBIZ-1999: ------------------------------------ Hans, thank you for testing the patch. The edit button is commented because the portlet parametrization is not yet implemented and not even designed. The edit button should show a form that should be specified with the portlet screen. This form should be used to set some parameters that would specify how the portlet will be displayed. For instance a project summary portlet could be parametrized with the particular project to be shown. About the possibility for the user to configure their pages, I think it would be something similar to what the user does now in the MyPage preferences where all the checkboxes are available. The difference is that the portal system is more general and will be extended as long as new portlet will be defined in the application components. > 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 > > > 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. |
[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=12644516#action_12644516 ] Jacques Le Roux commented on OFBIZ-1999: ---------------------------------------- Hi Bruno, I tried to apply the patch but got an error in line 305 > 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 > > > 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. |
[jira] Updated: (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 ] Bruno Busco updated OFBIZ-1999: ------------------------------- Attachment: portalPages.patch Hans, Jacques, please find an updated the patch built against the latest trunk. > 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 > > > 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. |
[jira] Updated: (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 ] Bruno Busco updated OFBIZ-1999: ------------------------------- Attachment: portalPages.patch In the new attached patch I have started to implement the portlet attributes editing. At this stage I would definitively like an expert review of the design and implementation. I also need help in completing the attribute editing. Is anybody interested and available to help? Many thanks, 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 > > > 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. |
[jira] Updated: (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 ] Bruno Busco updated OFBIZ-1999: ------------------------------- Attachment: portalPages.patch OK, moved a little further. Now the portlet edit form is able to retrieve and edit the portlet attributes in the database. What remains to do is to have the portlet screen to retrieve the attributes to be used. For this I have not yet a clear idea on the best way to do: The portlets are defined as regular screens. These are rendered by the pagePortal.ftl using the <render-screen> tag in a <#list>. To retrieve a portlet attribute map the getPortletAttribute servise must be called specifing the portalPageId, portalPortletId and sequenceId that identify the single portlet instance. How to make the ftl call the service to retrieve the attributes and pass them to the rendered screen? Many thanks for any idea! > 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 > > > 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. |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |