[
https://issues.apache.org/jira/browse/OFBIZ-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648867#action_12648867
]
Hans Bakker commented on OFBIZ-2052:
------------------------------------
Perhaps a little more of my intentions in moving from MyPage to MyPortal:
1. MyPortal will initially look the same as MyPage
2. Act as an example entry in ofbiz, for customers and employees or complete
new users without a role assigned.
3. All pages can be modified by adding or deleting portlets, even pages can be
added.
4. Create portlets for all the screens used in mypage and locate them in the
original components like Bruno proposes.
5. The preference button will allow you to add/delete portal pages and
add/delete/configure portalpages (look at the demo portal.diff file)
some other points:
1. My experience is that end users will use the system out of the box and 99%
will use the screens as proposed and will not modify them.
2. IT support people however can quickly help them modify them and create
specific pages/portlets for particular user groups.
This MyPage/Myportal function is an entry to the system showing that specific
screen compositions can easily be created for particular user groups, however
the portlet functions can surely be used in CRM or other components too.
Problem areas:
1. I am missing the default definition in the portal function which can be
used if a new user logs on.
2. Portlet list should only show portlets the user has access too.
As i mentioned i (with my people) can do this in about 4 weeks so this
transition period with MyPage/MyPortal only exist a short time and community
members can comment during the implementation.
> Convert Mypage into the Myportal component using the new portal functions
> -------------------------------------------------------------------------
>
> Key: OFBIZ-2052
> URL: https://issues.apache.org/jira/browse/OFBIZ-2052
> Project: OFBiz
> Issue Type: New Feature
> Components: specialpurpose/mypage
> Affects Versions: SVN trunk
> Reporter: Hans Bakker
> Fix For: SVN trunk
>
> Attachments: portal.diff
>
>
> Now the portal functions is in the trunk, i had a more closer look how to use
> this in the mypage component.
> The result is that I would like to propose a new component call "My Portal"
> which will replace the "My Page" component. This will give me the opportunity
> to slowly (in 3-4 weeks) make the conversion.
> Attached is a diff file when applied will create the first version of the new
> component showing the principle, how the portal functions could be used.
> When installed it will create a new tab called "my Portal" initially only
> with the default page.
> When you click on "preferences" you see a list of portal pages, and a form to
> add new ones.
> If a new one is added, also a new button will show for that page.
> When you click on the new page Id, the configuration screen appears and a
> portlet can be added and when there are more they can be shifted around.
> When no objections then i will commit this version and will extend it and
> finally will remove the mypage component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
