Thanks to Bruno's portal functions we have now a finished component
"MyPortal" which contains all the functions of the MyPage component and the portal functions added. "MyPage has been taken off the main menu" The user is presented with a number of system pages and portlets which can be completely changed by the user itself using thje preferences button on the right hand side of the application menu. The MyPortal component serves currently for 3 groups of users: 1. users not linked to any security group (just registered users via the myportal registration option) 2. users linked to the MYPORTAL_EMPLOYEE security group such as the login DemoEmployee or the user admin (password=ofbiz) 3. users linked to the MYPORTAL_CUSTOMER security group such as the login DemoCustomer (password=ofbiz) To add any other groups is relatively easy. examples are in the MyPortalTypeData.xml file. The next tasks will be to move all portlets in the myportal component back to the orginal component and add new portlets. Any comments, requests or faults found, please raise a Jira issue. these activities were sponsored by: http://www.antwebsystems.com : Quality OFBiz support for competitive rates... |
Sounds very nice. I asked once before but never got a response, is MyPortal
following the Java Portlet spec? I will merge right away! Regards, Sven 2009/2/11 Hans Bakker <[hidden email]> > Thanks to Bruno's portal functions we have now a finished component > "MyPortal" which contains all the functions of the MyPage component and > the portal functions added. "MyPage has been taken off the main menu" > > The user is presented with a number of system pages and portlets which > can be completely changed by the user itself using thje preferences > button on the right hand side of the application menu. > > The MyPortal component serves currently for 3 groups of users: > 1. users not linked to any security group (just registered users via the > myportal registration option) > 2. users linked to the MYPORTAL_EMPLOYEE security group such as the > login DemoEmployee or the user admin (password=ofbiz) > 3. users linked to the MYPORTAL_CUSTOMER security group such as the > login DemoCustomer (password=ofbiz) > > To add any other groups is relatively easy. examples are in the > MyPortalTypeData.xml file. > > The next tasks will be to move all portlets in the myportal component > back to the orginal component and add new portlets. > > Any comments, requests or faults found, please raise a Jira issue. > > these activities were sponsored by: > http://www.antwebsystems.com : > Quality OFBiz support for competitive rates... > > > |
On Feb 11, 2009, at 1:50 AM, Sven Wesley wrote: > Sounds very nice. I asked once before but never got a response, is > MyPortal > following the Java Portlet spec? What would it mean to follow the "Java Portlet spec"? -David |
In reply to this post by Sven Wesley
No, it is not.
I am pretty sure there was some discussion on that, but because this implementation tightly integrated with the ofbiz framework is was agreed we would not do this. Regards, Hans On Wed, 2009-02-11 at 09:50 +0100, Sven Wesley wrote: > Sounds very nice. I asked once before but never got a response, is MyPortal > following the Java Portlet spec? > > I will merge right away! > > Regards, > Sven > > 2009/2/11 Hans Bakker <[hidden email]> > > > Thanks to Bruno's portal functions we have now a finished component > > "MyPortal" which contains all the functions of the MyPage component and > > the portal functions added. "MyPage has been taken off the main menu" > > > > The user is presented with a number of system pages and portlets which > > can be completely changed by the user itself using thje preferences > > button on the right hand side of the application menu. > > > > The MyPortal component serves currently for 3 groups of users: > > 1. users not linked to any security group (just registered users via the > > myportal registration option) > > 2. users linked to the MYPORTAL_EMPLOYEE security group such as the > > login DemoEmployee or the user admin (password=ofbiz) > > 3. users linked to the MYPORTAL_CUSTOMER security group such as the > > login DemoCustomer (password=ofbiz) > > > > To add any other groups is relatively easy. examples are in the > > MyPortalTypeData.xml file. > > > > The next tasks will be to move all portlets in the myportal component > > back to the orginal component and add new portlets. > > > > Any comments, requests or faults found, please raise a Jira issue. > > > > these activities were sponsored by: > > http://www.antwebsystems.com : > > Quality OFBiz support for competitive rates... > > > > > > Antwebsystems.com: Quality OFBiz services for competitive prices |
In reply to this post by hans_bakker
That's great news Hans. This is neat stuff and I can't wait to play with it more. I'm glad you mentioned moving the portlets into applications or other specialpurpose components. I'd actually like to help with that as part of the more general effort to make the framework independent of the applications... and I think this MyPortal application would be great to have in the framework itself. Anyway, onward and upward! And, congrats. -David On Feb 11, 2009, at 12:24 AM, Hans Bakker wrote: > Thanks to Bruno's portal functions we have now a finished component > "MyPortal" which contains all the functions of the MyPage component > and > the portal functions added. "MyPage has been taken off the main menu" > > The user is presented with a number of system pages and portlets which > can be completely changed by the user itself using thje preferences > button on the right hand side of the application menu. > > The MyPortal component serves currently for 3 groups of users: > 1. users not linked to any security group (just registered users via > the > myportal registration option) > 2. users linked to the MYPORTAL_EMPLOYEE security group such as the > login DemoEmployee or the user admin (password=ofbiz) > 3. users linked to the MYPORTAL_CUSTOMER security group such as the > login DemoCustomer (password=ofbiz) > > To add any other groups is relatively easy. examples are in the > MyPortalTypeData.xml file. > > The next tasks will be to move all portlets in the myportal component > back to the orginal component and add new portlets. > > Any comments, requests or faults found, please raise a Jira issue. > > these activities were sponsored by: > http://www.antwebsystems.com : > Quality OFBiz support for competitive rates... > > |
In reply to this post by hans_bakker
My reply was somewhat of a loaded question, so I'm interested in Sven's answer, but the idea behind a JSR-168 portlet assumes using certain other tools like JSP that we simply don't use in OFBiz for very good reasons. I won't take the position that JSR-168/268 is not applicable to OFBiz, but if we were to do anything with it we would need some specific things to go after, like: 1. how (in detail) would OFBiz users benefit from JSR-168/268 support? for example, what would they be able to do that they could not otherwise? 2. how would the JSR-168/268 specifications be implemented in OFBiz and used internally in the project? or would they? 3. for cases of redundant technologies, what would we recommend to developers as best practices for selecting between the different technologies? -David On Feb 11, 2009, at 1:56 AM, Hans Bakker wrote: > No, it is not. > I am pretty sure there was some discussion on that, but because this > implementation tightly integrated with the ofbiz framework is was > agreed > we would not do this. > > Regards, > Hans > > On Wed, 2009-02-11 at 09:50 +0100, Sven Wesley wrote: >> Sounds very nice. I asked once before but never got a response, is >> MyPortal >> following the Java Portlet spec? >> >> I will merge right away! >> >> Regards, >> Sven >> >> 2009/2/11 Hans Bakker <[hidden email]> >> >>> Thanks to Bruno's portal functions we have now a finished component >>> "MyPortal" which contains all the functions of the MyPage >>> component and >>> the portal functions added. "MyPage has been taken off the main >>> menu" >>> >>> The user is presented with a number of system pages and portlets >>> which >>> can be completely changed by the user itself using thje preferences >>> button on the right hand side of the application menu. >>> >>> The MyPortal component serves currently for 3 groups of users: >>> 1. users not linked to any security group (just registered users >>> via the >>> myportal registration option) >>> 2. users linked to the MYPORTAL_EMPLOYEE security group such as the >>> login DemoEmployee or the user admin (password=ofbiz) >>> 3. users linked to the MYPORTAL_CUSTOMER security group such as the >>> login DemoCustomer (password=ofbiz) >>> >>> To add any other groups is relatively easy. examples are in the >>> MyPortalTypeData.xml file. >>> >>> The next tasks will be to move all portlets in the myportal >>> component >>> back to the orginal component and add new portlets. >>> >>> Any comments, requests or faults found, please raise a Jira issue. >>> >>> these activities were sponsored by: >>> http://www.antwebsystems.com : >>> Quality OFBiz support for competitive rates... >>> >>> >>> > -- > Antwebsystems.com: Quality OFBiz services for competitive prices > |
In reply to this post by David E Jones-3
Hi David,
glad to hear you liked it and of course any help is always appreciated! Regards, Hans On Wed, 2009-02-11 at 01:58 -0700, David E Jones wrote: > That's great news Hans. This is neat stuff and I can't wait to play > with it more. > > I'm glad you mentioned moving the portlets into applications or other > specialpurpose components. I'd actually like to help with that as part > of the more general effort to make the framework independent of the > applications... and I think this MyPortal application would be great > to have in the framework itself. > > Anyway, onward and upward! And, congrats. > > -David > > > On Feb 11, 2009, at 12:24 AM, Hans Bakker wrote: > > > Thanks to Bruno's portal functions we have now a finished component > > "MyPortal" which contains all the functions of the MyPage component > > and > > the portal functions added. "MyPage has been taken off the main menu" > > > > The user is presented with a number of system pages and portlets which > > can be completely changed by the user itself using thje preferences > > button on the right hand side of the application menu. > > > > The MyPortal component serves currently for 3 groups of users: > > 1. users not linked to any security group (just registered users via > > the > > myportal registration option) > > 2. users linked to the MYPORTAL_EMPLOYEE security group such as the > > login DemoEmployee or the user admin (password=ofbiz) > > 3. users linked to the MYPORTAL_CUSTOMER security group such as the > > login DemoCustomer (password=ofbiz) > > > > To add any other groups is relatively easy. examples are in the > > MyPortalTypeData.xml file. > > > > The next tasks will be to move all portlets in the myportal component > > back to the orginal component and add new portlets. > > > > Any comments, requests or faults found, please raise a Jira issue. > > > > these activities were sponsored by: > > http://www.antwebsystems.com : > > Quality OFBiz support for competitive rates... > > > > > Antwebsystems.com: Quality OFBiz services for competitive prices |
In reply to this post by David E Jones-3
Loaded? Nah, but indeed interesting. On the other hand I already got an
answer that fits me (No, that is. Thanks Hans). 1. For example reusage of components from other systems, which is the idea of the concept with the Portlet spec. A portlet for Liferay would in that case work in Ofbiz too - or in any other portal that supports portlets. 2. Luckily, I hope that my customer wants to _not_ use their old portlets and instead make new portlet-style components in Flex (reusable almost everywhere), so I haven't thought about it yet. In worst case I have to. 3. I believe "redundancy in technology" is not a good thing, in Ofbiz there is a lot of redundancy alreday so I would not prefer to add more of that cake. In any case, the MyPortal is awaited from my point of view. 2009/2/11 David E Jones <[hidden email]> > > My reply was somewhat of a loaded question, so I'm interested in Sven's > answer, but the idea behind a JSR-168 portlet assumes using certain other > tools like JSP that we simply don't use in OFBiz for very good reasons. > > I won't take the position that JSR-168/268 is not applicable to OFBiz, but > if we were to do anything with it we would need some specific things to go > after, like: > > 1. how (in detail) would OFBiz users benefit from JSR-168/268 support? for > example, what would they be able to do that they could not otherwise? > > 2. how would the JSR-168/268 specifications be implemented in OFBiz and > used internally in the project? or would they? > > 3. for cases of redundant technologies, what would we recommend to > developers as best practices for selecting between the different > technologies? > > -David > > > |
Free forum by Nabble | Edit this page |