[
https://issues.apache.org/jira/browse/OFBIZ-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648761#action_12648761
]
Bruno Busco commented on OFBIZ-2052:
------------------------------------
I have created this page on Confluence:
http://docs.ofbiz.org/display/OFBIZ/Customizing+the+Dashboard
trying to share ideas of how the Dashboard could be used.
Of course it is only a proposal even is it is in the form of and end-user
documentation. This is because it is strictly related to UI.
This dashboard use model foresees that the dashboard is reached as the first
page the user has access to when logging into OFBiz but other solutions can
work also.
Originally I put the dashboard request into the common-controller to have it
reached by all the applications. Mau be this can be done when the dashboard is
stable and well tested.
I had put a link to the dashboard page in the ofbiz logo also.
What I suggest about the MyPage conversion is this:
1) Lets make all the portlets implemented in the MyPage component leaving the
MyPage as it is now and only enebling the new declared portlets to be added in
the dashboard in the example application. Doing this we could test the
dashboard AND the new defined portlets without hurting the MyPage application
itself.
2) When the dashboard is stable we could have it reached as home page.
3) At this stage the MyPage component could be disabled from the Application
Tab but left as component because it will provide the portlets to the dashboard
system.
> 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.
