[jira] Created: (OFBIZ-1999) A portal/portlet implementation
Locked
1234
1234
[jira] Created: (OFBIZ-1999) A portal/portlet implementation
 
|
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: portal.zip 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
|
|
[ https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Busco updated OFBIZ-1999: ------------------------------- Attachment: portal.zip At the moment this is implemented as an hot-deploy 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: portal.zip > > > 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: screenshot-1.jpg This is how the portal appears when the portalConfigure option is active. Every portlet is surrounded by a screenlet that shows the portlet name and some controls to move the portlet around the portal or to a different portal. > 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: portal.zip, screenshot-1.jpg > > > Hi devs, > I am trying to set up a portal/portlet model similar to what is implemented into JIRA user interface. > The Idea is that every component can "register" its selected screens as system portlets using something like: > <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" screenPath="component://portal/widget/CommonScreens.xml#welcome" /> > In this case the portal component has registered a welcome screen as "WELCOME" portlet. > The portlets can later be "mounted" into portals with the entity: > <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME" columnNum="1" sequenceNum="1" /> > <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN" columnNum="2" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001" columnNum="1" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002" columnNum="3" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003" columnNum="1" sequenceNum="2" /> > In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and with the indicated order. > Every portal is defined by the entity: > <Portal portalId="DEFAULT" name="Default home portal" description="The default OFBiz portal" owner="admin" /> > And is related to a specific user. So every user can have as many portals he needs and a DEFAULT portal can be defined by the admin. > In the attached zip file there is a very draft implementation of this that I would like so submit to your attention to share ideas about it and eventually develop together. > Many thanks for your feedbacks, > Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[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: screenshot-2.jpg screenshot-2 shows how the same portal appears when the configurePortal variable is set to "" into the portal.groovy file. This should be toggled by the configure button on the application bar. > 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: portal.zip, screenshot-1.jpg, screenshot-2.jpg > > > Hi devs, > I am trying to set up a portal/portlet model similar to what is implemented into JIRA user interface. > The Idea is that every component can "register" its selected screens as system portlets using something like: > <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" screenPath="component://portal/widget/CommonScreens.xml#welcome" /> > In this case the portal component has registered a welcome screen as "WELCOME" portlet. > The portlets can later be "mounted" into portals with the entity: > <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME" columnNum="1" sequenceNum="1" /> > <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN" columnNum="2" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001" columnNum="1" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002" columnNum="3" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003" columnNum="1" sequenceNum="2" /> > In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and with the indicated order. > Every portal is defined by the entity: > <Portal portalId="DEFAULT" name="Default home portal" description="The default OFBiz portal" owner="admin" /> > And is related to a specific user. So every user can have as many portals he needs and a DEFAULT portal can be defined by the admin. > In the attached zip file there is a very draft implementation of this that I would like so submit to your attention to share ideas about it and eventually develop together. > Many thanks for your feedbacks, > Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[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=12639984#action_12639984 ] David E. Jones commented on OFBIZ-1999: --------------------------------------- This looks really cool Bruno. You're timing is great as I've been looking into this recently and have some ideas for design, which is pretty close to what you've put together here. I'll write those up and attach them here in a bit. One difference to consider is the term "portal page" instead of "portal" which kind of refers to a collections of pages or the system that runs the portal pages. In a way the ControlServlet + the Screen Widget makes a nice portal system, well at least with enhancements like you're going for here. For general feedback, I like the way you've made this configurable and also still use the screen widget and such. Really cool stuff, and I'd love to see this going soon. > 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: portal.zip, screenshot-1.jpg, screenshot-2.jpg > > > Hi devs, > I am trying to set up a portal/portlet model similar to what is implemented into JIRA user interface. > The Idea is that every component can "register" its selected screens as system portlets using something like: > <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" screenPath="component://portal/widget/CommonScreens.xml#welcome" /> > In this case the portal component has registered a welcome screen as "WELCOME" portlet. > The portlets can later be "mounted" into portals with the entity: > <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME" columnNum="1" sequenceNum="1" /> > <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN" columnNum="2" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001" columnNum="1" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002" columnNum="3" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003" columnNum="1" sequenceNum="2" /> > In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and with the indicated order. > Every portal is defined by the entity: > <Portal portalId="DEFAULT" name="Default home portal" description="The default OFBiz portal" owner="admin" /> > And is related to a specific user. So every user can have as many portals he needs and a DEFAULT portal can be defined by the admin. > In the attached zip file there is a very draft implementation of this that I would like so submit to your attention to share ideas about it and eventually develop together. > Many thanks for your feedbacks, > Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[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=12639989#action_12639989 ] Vince Clark commented on OFBIZ-1999: ------------------------------------ Have you considered integrating a portal that already exists? It seems to me that if there is an open source portal that is technology and license friendly it would make sense to try and leverage that. In a mature portal there would be residual benefits like skinable look and feel, maybe other nice UI features like drag and drop, and an established community. > 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: portal.zip, screenshot-1.jpg, screenshot-2.jpg > > > Hi devs, > I am trying to set up a portal/portlet model similar to what is implemented into JIRA user interface. > The Idea is that every component can "register" its selected screens as system portlets using something like: > <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" screenPath="component://portal/widget/CommonScreens.xml#welcome" /> > In this case the portal component has registered a welcome screen as "WELCOME" portlet. > The portlets can later be "mounted" into portals with the entity: > <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME" columnNum="1" sequenceNum="1" /> > <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN" columnNum="2" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001" columnNum="1" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002" columnNum="3" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003" columnNum="1" sequenceNum="2" /> > In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and with the indicated order. > Every portal is defined by the entity: > <Portal portalId="DEFAULT" name="Default home portal" description="The default OFBiz portal" owner="admin" /> > And is related to a specific user. So every user can have as many portals he needs and a DEFAULT portal can be defined by the admin. > In the attached zip file there is a very draft implementation of this that I would like so submit to your attention to share ideas about it and eventually develop together. > Many thanks for your feedbacks, > Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[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=12639992#action_12639992 ] David E. Jones commented on OFBIZ-1999: --------------------------------------- Here are my notes so far. As I mentioned they are pretty similar to what Bruno has put together, which is very cool: Basic Entity Model (not fleshed out all the way, mostly general structure): PortalPortlet -portalPortletId* -screenLocation -portletName (possibly use screen name if empty, or just leave this field out) PortalPage -portalPageId* PortalPageColumn -portalPageId* -columnSeqId* -columnWidthPixels: numeric -columnWidthPercentage: numeric PortalPagePortlet -portalPageId* -portalPortletId* -columnSeqId: id (note: could be part of pk, would make it always required and allow a particular portlet to be on the page multiple time in different columns, which might be weird) -sequenceInColumn: numeric New Screen Widget "widget element": include-portal-page, attributes: portalPageId The portalPageId value should be expandable so that a variable can be used, possibly driven by a drop-down or other UI element so the user can select among various portal pages. Could also have a ControlServlet view handler for portal page, but would have problems with decoration that using a simple screen widget include element would take care of. 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 > Priority: Minor > Attachments: portal.zip, screenshot-1.jpg, screenshot-2.jpg > > > Hi devs, > I am trying to set up a portal/portlet model similar to what is implemented into JIRA user interface. > The Idea is that every component can "register" its selected screens as system portlets using something like: > <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" screenPath="component://portal/widget/CommonScreens.xml#welcome" /> > In this case the portal component has registered a welcome screen as "WELCOME" portlet. > The portlets can later be "mounted" into portals with the entity: > <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME" columnNum="1" sequenceNum="1" /> > <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN" columnNum="2" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001" columnNum="1" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002" columnNum="3" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003" columnNum="1" sequenceNum="2" /> > In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and with the indicated order. > Every portal is defined by the entity: > <Portal portalId="DEFAULT" name="Default home portal" description="The default OFBiz portal" owner="admin" /> > And is related to a specific user. So every user can have as many portals he needs and a DEFAULT portal can be defined by the admin. > In the attached zip file there is a very draft implementation of this that I would like so submit to your attention to share ideas about it and eventually develop together. > Many thanks for your feedbacks, > Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[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=12640068#action_12640068 ] Bruno Busco commented on OFBIZ-1999: ------------------------------------ David, I am really happy for the positive feedback and perfectly agree on your notes. At the moment the implementation I attached was really draft but I preferred to communicate the idea to the community becouse I think that the efforts we are going to spend in orther to have the MyPage application more general could be spent on the PagePortal stuff. A PagePortal could then be used as users's MyPage. An additional feature that I was thinking to add in the model at a later stage was the PortalPortlet configuration. With this I mean that a PagePortlet instance in a PagePortal could be configured in a different way from another instance of the same PortalPortlet. For instance a PortalPortlet that lists the last user communications can be configured to show the last 10 or 20 communications and this is up to the user that configures his PortalPage. To to this I was thinking to add a "configureFormLocation" in the PortalPortlet entity to link a form to the PortapPortlet. This will be used when the user press the "edit" button on the PortalPortlet configuration bar. At the moment I have no idea of how the configured parameters could be saved in the database (in which entity) and passed to the PortalPortlet screen to affect the rendering. > 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: portal.zip, screenshot-1.jpg, screenshot-2.jpg > > > Hi devs, > I am trying to set up a portal/portlet model similar to what is implemented into JIRA user interface. > The Idea is that every component can "register" its selected screens as system portlets using something like: > <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" screenPath="component://portal/widget/CommonScreens.xml#welcome" /> > In this case the portal component has registered a welcome screen as "WELCOME" portlet. > The portlets can later be "mounted" into portals with the entity: > <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME" columnNum="1" sequenceNum="1" /> > <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN" columnNum="2" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001" columnNum="1" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002" columnNum="3" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003" columnNum="1" sequenceNum="2" /> > In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and with the indicated order. > Every portal is defined by the entity: > <Portal portalId="DEFAULT" name="Default home portal" description="The default OFBiz portal" owner="admin" /> > And is related to a specific user. So every user can have as many portals he needs and a DEFAULT portal can be defined by the admin. > In the attached zip file there is a very draft implementation of this that I would like so submit to your attention to share ideas about it and eventually develop together. > Many thanks for your feedbacks, > Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[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=12640070#action_12640070 ] Bruno Busco commented on OFBIZ-1999: ------------------------------------ Vince, before starting this work I looked at the Apache pluto project that was indicated on the ML. Assuming as requirement to build up a PagePortal system as the JIRA one (sorry but I am still a JIRA fan) I considered that into OFBiz there was almost everything needed. Of course this conclusion could be driven by my little knowledge of the Pluto project but at least I considered it for a moment! ;-) > 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: portal.zip, screenshot-1.jpg, screenshot-2.jpg > > > Hi devs, > I am trying to set up a portal/portlet model similar to what is implemented into JIRA user interface. > The Idea is that every component can "register" its selected screens as system portlets using something like: > <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" screenPath="component://portal/widget/CommonScreens.xml#welcome" /> > In this case the portal component has registered a welcome screen as "WELCOME" portlet. > The portlets can later be "mounted" into portals with the entity: > <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME" columnNum="1" sequenceNum="1" /> > <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN" columnNum="2" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001" columnNum="1" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002" columnNum="3" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003" columnNum="1" sequenceNum="2" /> > In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and with the indicated order. > Every portal is defined by the entity: > <Portal portalId="DEFAULT" name="Default home portal" description="The default OFBiz portal" owner="admin" /> > And is related to a specific user. So every user can have as many portals he needs and a DEFAULT portal can be defined by the admin. > In the attached zip file there is a very draft implementation of this that I would like so submit to your attention to share ideas about it and eventually develop together. > Many thanks for your feedbacks, > Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[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, in the attached portalPage.patch file I have changed the entity names as suggested by David and tryed to better integrate into the framework. A new "portalPage" request has been added to the common-controller and a "Portal" menu item has been added in the commonAppMenu. Two demo portlets have been added into the common component. I would like to discuss if you think this is the correct way of adding the portlet feature to the system. > 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: portal.zip, portalPages.patch, screenshot-1.jpg, screenshot-2.jpg > > > Hi devs, > I am trying to set up a portal/portlet model similar to what is implemented into JIRA user interface. > The Idea is that every component can "register" its selected screens as system portlets using something like: > <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" screenPath="component://portal/widget/CommonScreens.xml#welcome" /> > In this case the portal component has registered a welcome screen as "WELCOME" portlet. > The portlets can later be "mounted" into portals with the entity: > <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME" columnNum="1" sequenceNum="1" /> > <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN" columnNum="2" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001" columnNum="1" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002" columnNum="3" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003" columnNum="1" sequenceNum="2" /> > In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and with the indicated order. > Every portal is defined by the entity: > <Portal portalId="DEFAULT" name="Default home portal" description="The default OFBiz portal" owner="admin" /> > And is related to a specific user. So every user can have as many portals he needs and a DEFAULT portal can be defined by the admin. > In the attached zip file there is a very draft implementation of this that I would like so submit to your attention to share ideas about it and eventually develop together. > Many thanks for your feedbacks, > Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[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 Proceding on PortalPage stuff. Any comments/help will be appreciated. - Added service to add a portalPortlet to a portalPage (no permission check yet). This is available on the UI on the "Add portlet..." button that shows up when configure mode is ON - Added service to remove a portalPortlet from a portalPage (no permission check yet) This is available on the UI on the "X" button on the portlet title bar that shows up when configure mode is ON - Added a portalPortletLookup screen to select the portlet to add between the available portlets - Defined a new "MyPage" portalPage - Added several portlets definition in the MyPage component and included by default in the MyPage portalPage > 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: portal.zip, portalPages.patch, portalPages.patch, screenshot-1.jpg, screenshot-2.jpg > > > Hi devs, > I am trying to set up a portal/portlet model similar to what is implemented into JIRA user interface. > The Idea is that every component can "register" its selected screens as system portlets using something like: > <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" screenPath="component://portal/widget/CommonScreens.xml#welcome" /> > In this case the portal component has registered a welcome screen as "WELCOME" portlet. > The portlets can later be "mounted" into portals with the entity: > <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME" columnNum="1" sequenceNum="1" /> > <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN" columnNum="2" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001" columnNum="1" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002" columnNum="3" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003" columnNum="1" sequenceNum="2" /> > In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and with the indicated order. > Every portal is defined by the entity: > <Portal portalId="DEFAULT" name="Default home portal" description="The default OFBiz portal" owner="admin" /> > And is related to a specific user. So every user can have as many portals he needs and a DEFAULT portal can be defined by the admin. > In the attached zip file there is a very draft implementation of this that I would like so submit to your attention to share ideas about it and eventually develop together. > Many thanks for your feedbacks, > Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[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=12640705#action_12640705 ] Bruno Busco commented on OFBIZ-1999: ------------------------------------ At least we still need: - The portalPage manage page where a new portalPage can be created or the name can be edited - Service to move the portalPortlet around in the portalPage - Permission checking - Lot of nice CSS A further step could be to implement: - Portlet configuration by means of an associated form - New Screen Widget "widget element": include-portal-page, attributes: portalPageId > 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: portal.zip, portalPages.patch, portalPages.patch, screenshot-1.jpg, screenshot-2.jpg > > > Hi devs, > I am trying to set up a portal/portlet model similar to what is implemented into JIRA user interface. > The Idea is that every component can "register" its selected screens as system portlets using something like: > <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" screenPath="component://portal/widget/CommonScreens.xml#welcome" /> > In this case the portal component has registered a welcome screen as "WELCOME" portlet. > The portlets can later be "mounted" into portals with the entity: > <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME" columnNum="1" sequenceNum="1" /> > <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN" columnNum="2" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001" columnNum="1" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002" columnNum="3" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003" columnNum="1" sequenceNum="2" /> > In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and with the indicated order. > Every portal is defined by the entity: > <Portal portalId="DEFAULT" name="Default home portal" description="The default OFBiz portal" owner="admin" /> > And is related to a specific user. So every user can have as many portals he needs and a DEFAULT portal can be defined by the admin. > In the attached zip file there is a very draft implementation of this that I would like so submit to your attention to share ideas about it and eventually develop together. > Many thanks for your feedbacks, > Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[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: - Added services to move portalPortlets around in the portalPage - Added services to move portalPortlets in a different portalPage - Added services to create and update portalPages - Added ManagePortal Screen to edit name/description of the portalPage and to create new portalPage - Aligned portlets vertically in the portalPage - Used a drop-down to switch between the available portalPages Still to implement: - Permission check - Better LOGIN portlet (this should switch automatically between username/password request and user info/preferences if we are logged in or not) - Better MYPAGE portlets - CSS - Portlet configuration by means of an associated form - New Screen Widget "widget element": include-portal-page, attributes: portalPageId Thank you for any hint / comment / review > A portal/portlet implementation > ------------------------------- > > Key: OFBIZ-1999 > URL: https://issues.apache.org/jira/browse/OFBIZ-1999 > Project: OFBiz > Issue Type: New Feature > Components: ALL COMPONENTS > Reporter: Bruno Busco > Priority: Minor > Attachments: portalPages.patch, portalPages.patch, portalPages.patch, screenshot-1.jpg, screenshot-2.jpg > > > Hi devs, > I am trying to set up a portal/portlet model similar to what is implemented into JIRA user interface. > The Idea is that every component can "register" its selected screens as system portlets using something like: > <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" screenPath="component://portal/widget/CommonScreens.xml#welcome" /> > In this case the portal component has registered a welcome screen as "WELCOME" portlet. > The portlets can later be "mounted" into portals with the entity: > <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME" columnNum="1" sequenceNum="1" /> > <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN" columnNum="2" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001" columnNum="1" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002" columnNum="3" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003" columnNum="1" sequenceNum="2" /> > In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and with the indicated order. > Every portal is defined by the entity: > <Portal portalId="DEFAULT" name="Default home portal" description="The default OFBiz portal" owner="admin" /> > And is related to a specific user. So every user can have as many portals he needs and a DEFAULT portal can be defined by the admin. > In the attached zip file there is a very draft implementation of this that I would like so submit to your attention to share ideas about it and eventually develop together. > Many thanks for your feedbacks, > Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[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: portal.zip) > A portal/portlet implementation > ------------------------------- > > Key: OFBIZ-1999 > URL: https://issues.apache.org/jira/browse/OFBIZ-1999 > Project: OFBiz > Issue Type: New Feature > Components: ALL COMPONENTS > Reporter: Bruno Busco > Priority: Minor > Attachments: portalPages.patch, portalPages.patch, portalPages.patch, screenshot-1.jpg, screenshot-2.jpg > > > Hi devs, > I am trying to set up a portal/portlet model similar to what is implemented into JIRA user interface. > The Idea is that every component can "register" its selected screens as system portlets using something like: > <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" screenPath="component://portal/widget/CommonScreens.xml#welcome" /> > In this case the portal component has registered a welcome screen as "WELCOME" portlet. > The portlets can later be "mounted" into portals with the entity: > <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME" columnNum="1" sequenceNum="1" /> > <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN" columnNum="2" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001" columnNum="1" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002" columnNum="3" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003" columnNum="1" sequenceNum="2" /> > In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and with the indicated order. > Every portal is defined by the entity: > <Portal portalId="DEFAULT" name="Default home portal" description="The default OFBiz portal" owner="admin" /> > And is related to a specific user. So every user can have as many portals he needs and a DEFAULT portal can be defined by the admin. > In the attached zip file there is a very draft implementation of this that I would like so submit to your attention to share ideas about it and eventually develop together. > Many thanks for your feedbacks, > Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[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, portalPages.patch, portalPages.patch, portalPages.patch, screenshot-1.jpg, screenshot-2.jpg > > > Hi devs, > I am trying to set up a portal/portlet model similar to what is implemented into JIRA user interface. > The Idea is that every component can "register" its selected screens as system portlets using something like: > <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" screenPath="component://portal/widget/CommonScreens.xml#welcome" /> > In this case the portal component has registered a welcome screen as "WELCOME" portlet. > The portlets can later be "mounted" into portals with the entity: > <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME" columnNum="1" sequenceNum="1" /> > <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN" columnNum="2" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001" columnNum="1" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002" columnNum="3" sequenceNum="2" /> > <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003" columnNum="1" sequenceNum="2" /> > In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and with the indicated order. > Every portal is defined by the entity: > <Portal portalId="DEFAULT" name="Default home portal" description="The default OFBiz portal" owner="admin" /> > And is related to a specific user. So every user can have as many portals he needs and a DEFAULT portal can be defined by the admin. > In the attached zip file there is a very draft implementation of this that I would like so submit to your attention to share ideas about it and eventually develop together. > Many thanks for your feedbacks, > Bruno -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[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: screenshot-1.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 > > > 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 > > > 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: screenshot-2.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 > > > 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 Fixed a wrong link in the addPortlet Lookup screen. > 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=12640820#action_12640820 ] Hans Bakker commented on OFBIZ-1999: ------------------------------------ Looking good Bruno, looking forward to help when required to have the current myPage functionality using your portal functionality.... > 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. |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |