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

Reply via email to