ofbiz-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Le Roux (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OFBIZ-1999) A portal/portlet implementation
Date Sat, 15 Nov 2008 08:52:45 GMT

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

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

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

> A portal/portlet implementation
> -------------------------------
>
>                 Key: OFBIZ-1999
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1999
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: ALL COMPONENTS
>            Reporter: Bruno Busco
>            Priority: Minor
>         Attachments: portalPage-configure-off.jpg, portalPage-configure-on.jpg, portalPageImages.zip,
portalPages.patch, portalPages.patch, portalPages.patch, portalPages.patch, portalPages.patch,
portalPages.patch, portalPages.patch, portalPages.patch, portalPages.patch, portalPages.patch,
portalPages.patch
>
>
> Hi devs,
> I am trying to set up a portal/portlet model similar to what is implemented into JIRA
user interface.
> The Idea is that every component can "register" its selected screens as system portlets
using something like:
> <Portlet portletId="WELCOME" name="Welcome" description="Welcome message" screenPath="component://portal/widget/CommonScreens.xml#welcome"
/>
> In this case the portal component has registered a welcome screen as "WELCOME" portlet.
> The portlets can later be "mounted" into portals with the entity:
>     <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME"      columnNum="1" sequenceNum="1"
/>
>     <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN"        columnNum="2" sequenceNum="2"
/>
>     <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001"   columnNum="1" sequenceNum="2"
/>
>     <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002"   columnNum="3" sequenceNum="2"
/>
>     <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003"   columnNum="1" sequenceNum="2"
/>
> In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and PORTLET003 are mounted
into the DEFAULT portal into the indicated solumns and with the indicated order.
> Every portal is defined by the entity:
> <Portal portalId="DEFAULT" name="Default home portal" description="The default OFBiz
portal" owner="admin" />
> And is related to a specific user. So every user can have as many portals he needs and
a DEFAULT portal can be defined by the admin.
> In the attached zip file there is a very draft implementation of this that I would like
so submit to your attention to share ideas about it and eventually develop together.
> Many thanks for your feedbacks,
> Bruno

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


Mime
View raw message