Thank you for your clarification Anil. I can see I was confused. I thought this
was a part of the portable device UI movement.
I like your proposal. We have created role-oriented UIs here by copying and
modifying existing files. Your approach would be simpler. I look forward to
seeing your contribution.
Anil Patel wrote:
> Adrian,
> This may not be help for applications for portable devices, At times we
> need
> applications that use screens from one or more ofbiz core components and
> assemble a cohesive tool set for certain role in company. E.g I am doing a
> asset maintenance application that needs Fixed Asset screens from
> Accounting, Screens for defining and managing Products like for Parts and
> Products that define the spec of Fixed Asset. There are few screens needed
> from Facility Manager for Inventory management, some from Party for
> managing
> Employees, Vendor, Manufacturer etc.
> Once this app reaches certain usable level I'll contribute the code to
> community for review. Hope I answered your question.
>
> Regards
> Anil Patel
>
>
> On 12/8/06, Adrian Crum <
[hidden email]> wrote:
>
>>
>> I'd like to see what others have to say about this subject.
>>
>> The question is: How can we accomodate OFBiz running on portable devices
>> without
>> re-writing the entire UI? Is that even possible?
>>
>> How does "parameterizing the location of decorators" help this effort?
>> I'm
>> not
>> clear on how such a thing would be implemented.
>>
>>
>> Anil Patel wrote:
>> > Hi,
>> > Is it Ok to parameterize location of decorators that are derived from
>> > main-decorator. By doing this special purpose applications will be able
>> > customize tab bar and few others things without having to copy bunch of
>> > screen code form Ofbiz main components.
>> >
>> > If this seems to be acceptable Idea and then I'll like to submit patch
>> to
>> > parameterize screens in accounting, product/catalog, facility.
>> >
>> > Regards
>> > Anil Patel
>> >
>>
>
Locked
