What i meant is this line:
<include-screen name="ApplicationDecorator"
location="component://commonext/widget/CommonScreens.xml"/>
which is round in CommonScreens.xml in the party module. It is using the
one in commonext, which includes some logic checking to allow the Setup
menu to appear. However if you create a new custom component in the
hot-deploy folder using the ant task, the common screens in it is defaulted
to use the one in common, rather than commonext.
Thanx
FooShyn
On Tue, Dec 20, 2011 at 7:09 AM, Jacques Le Roux <
[hidden email]> wrote:
> What do you call commonext screen exactly? (I don't see any "commonext"
> screen in OFBiz)
>
>
> Jacques
>
> From: "Foo Shyn Chung" <
[hidden email]>
>
>> Ah i think i found out what's the issue. The component that i'd created is
>> not using the commonext screen as the common screen, thus giving out this
>> behaviour.
>>
>> Would it be better if the ant task that creates custom components in
>> hot-deploy folder be generating the common screen using the one in
>> commonext rather than the common ones?
>>
>> Thanx
>> FooShyn
>>
>> On Fri, Dec 16, 2011 at 12:50 PM, Jacques Le Roux <
>>
[hidden email]> wrote:
>>
>> IIRW, it's depends on data you use. It's supposed to show only when you
>>> don't seed with demo data (ie only seed and such). Which makes sense
>>> since
>>> you are supposed to provide your own data...
>>> Did you cross another behaviour?
>>>
>>> Jacques
>>>
>>> From: "Foo Shyn Chung" <
[hidden email]>
>>>
>>> Hi guys,
>>>
>>>>
>>>> I notice that when i click on the Party or My Portal component, the
>>>> Setup
>>>> component is not appearing in the main app bar. However when i click on
>>>> other components, including those that i'd created in hot-deploy folder,
>>>> the Setup menu will appear.
>>>>
>>>> Would like to know how ofbiz control the main app bar for Setup so that
>>>> it
>>>> will only appear in certain scenario? Does it meant to be working in
>>>> this
>>>> way?
>>>>
>>>> Thanks
>>>> FooShyn
>>>>
>>>>
>>>>
>>
Locked
