Hi Bruno, currently the framework and the ERP application on top of it, have different target audiences and users.
The example component is a showcase of the framework and the myPortal component is a special component showing specific portalpages with specific portlets for the specific kind of users of the ERP application. So software developers vs ERP users... I would like to suggest to keep it as it is now: the example component for the framework and the MyPortal for the ERP application. Regards, Hans On Tue, 2008-12-23 at 09:45 +0100, Bruno Busco wrote: > Many thanks David and Hans for your feedbacks. > Of course for "vs." I did not mean "against". I am more than happy > with this collaborating experience. > > What I meant was: > In a framework-only release (which I am now working on) it could be > cool to have a "home" page where the user lands when it logs in. This > could be mounted to "/" and could be just a PortalPage with some > framework-defined portlets. > > If we agree on this, we could also think that the "home" page, in a > full OFBiz installation, could be the same but simply hosting more > (application-defined) portlets, still mounted on "/". > > Now, in this scenario, what will be the difference between the > MyPortal application and this application-powered-up "home" portal? > > I hope that now, with this explanation, the reason why I see an > overlapping between MyPortal and a framework home is more clear. > > I perfectly agree with the pattern we are outlining (portals in every > main application screen or everywhere needed). I think it is very > important to focus it so that future development will be done > according to it (hopefully ;-) ) > > Can I summarize like this what we are going to do ? > > 1) Since we are going to have many Configurable screens we should > think to define a Decorator for this. > 2) Framework should define a "home" application mounted (by default) > on "/". This application is just a one configurable screen (Portal). > 3) Every (or almost) application main page should be a configurable > screen and the actual main page content should be redefined as > portlets. > > Do you agree? > > -Bruno > > > 2008/12/23 Hans Bakker <mailingl...@antwebsystems.com>: > > Hi Bruno, > > > > First of all i think this development is a nice example of community > > collaboration. Started with the MyPage development, then the portal > > functions and in the end merging everything together and I expect it > > will not stop there. > > > > I expect that these portal functions will be used in many places in > > OFBiz. Not only as a framework dashboard, but also as a logged-on user > > oriented MyPortal component and more. Wouldn't it be nice to have every > > 'overview' page being configurable like the party profile page? Most > > people are only interested in certain screenlets of that page and > > certainly not at all, the same is true for the invoice overview, payment > > overview, project overview, quote overview etc etc.... > > > > The next thing we can think about is the starting 'main' page of every > > component. This page should give you the current status of the data in > > that component. Also here it is impossible to have a 'one page fits all' > > version. A user should be able to modify that. > > > > So i see the portal functions useful in many places....... so not > > 'MyPortal vs. framework dashboard' but your 'framework portal/portlet > > functions' being used in many places.... > > > > Regards, > > Hans > > > > > > -- > > Antwebsystems.com: Quality OFBiz services for competitive prices > > > > -- Antwebsystems.com: Quality OFBiz services for competitive prices
