discussion: moving myportal in commonext, add public portlets and set as root.

[Hans Bakker]

Community opinion?

We are thinking about moving the myportal component into the commonext
application component as an application and let it be the root webapp.

At the moment only the login menu is shown, however we could also add
here some 'public' portlets showing documentation, text and links about
the OFBiz system which in the end could be the OFBiz public website?

--
http://www.antwebsystems.com :
Quality OFBiz support for competitive rates....

[Scott Gray-2]

Hi Hans

On 9/09/2009, at 2:31 PM, Hans Bakker wrote:

> Community opinion?
>
> We are thinking about moving the myportal component into the commonext
> application component as an application and let it be the root webapp.

I'm sorry I don't understand why would it be necessary to move it to  
the commonext component?

> At the moment only the login menu is shown, however we could also add
> here some 'public' portlets showing documentation, text and links  
> about
> the OFBiz system which in the end could be the OFBiz public website?

I thought the plan was to use the content app for the ofbiz.apache.org  
site?

Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

[Bruno Busco]

+1 for moving myportal in the commonext and make it the root webapp so
that it will be available in a framework-only installation.
Several other framework-related portlets will come (i.e. user logins
and permissions list) and will be available to be used in a
framework-only installation.

-Bruno

2009/9/9 Scott Gray <[hidden email]>:

> Hi Hans
>
> On 9/09/2009, at 2:31 PM, Hans Bakker wrote:
>
>> Community opinion?
>>
>> We are thinking about moving the myportal component into the commonext
>> application component as an application and let it be the root webapp.
>
> I'm sorry I don't understand why would it be necessary to move it to the
> commonext component?
>
>> At the moment only the login menu is shown, however we could also add
>> here some 'public' portlets showing documentation, text and links about
>> the OFBiz system which in the end could be the OFBiz public website?
>
> I thought the plan was to use the content app for the ofbiz.apache.org site?
>
> Regards
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>

[David E. Jones-2]

The direction I liked best way back when was to put this in the  
framework itself, probably in the widget component because this  
depends on the screen widget and the screen widget does (or will)  
depend on it.

Anyway, I mention that because I agree with what Bruno wrote except  
that commonext is an applications component and this would be better  
in the framework, IMNSHO.

-David


On Sep 13, 2009, at 12:40 AM, Bruno Busco wrote:

> +1 for moving myportal in the commonext and make it the root webapp so
> that it will be available in a framework-only installation.
> Several other framework-related portlets will come (i.e. user logins
> and permissions list) and will be available to be used in a
> framework-only installation.
>
> -Bruno
>
> 2009/9/9 Scott Gray <[hidden email]>:
>> Hi Hans
>>
>> On 9/09/2009, at 2:31 PM, Hans Bakker wrote:
>>
>>> Community opinion?
>>>
>>> We are thinking about moving the myportal component into the  
>>> commonext
>>> application component as an application and let it be the root  
>>> webapp.
>>
>> I'm sorry I don't understand why would it be necessary to move it  
>> to the
>> commonext component?
>>
>>> At the moment only the login menu is shown, however we could also  
>>> add
>>> here some 'public' portlets showing documentation, text and links  
>>> about
>>> the OFBiz system which in the end could be the OFBiz public website?
>>
>> I thought the plan was to use the content app for the ofbiz.apache.org
>>  site?
>>
>> Regards
>> Scott
>>
>> HotWax Media
>> http://www.hotwaxmedia.com
>>