ofbiz-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Crum <adri...@hlmksw.com>
Subject Re: About issue: Clean up labels between order and ecommerce application (OFBIZ-1780)
Date Mon, 19 May 2008 15:23:39 GMT
Or maybe we could assume the components in the specialpurpose folder 
intend to override labels and just ignore those UI label files.


Bruno Busco wrote:
> Adrian,
> thank you, now I see what the label overriding is used for !
> In this case I would suggest to have all the overriding labels to be
> contained in a specific UiLabel file (that could for example be called
> _AppName_OverrideUiLabels.xml).
> This could be a standard method to be used in every case a label must be
> overridden.
> In the Asset Maintenance component there will be a AssetMaintUiLabels.xml
> file that will define all NEW labels for the component (no duplication is
> admitted here) and a AssetMaintOverrideUiLabels.xml file with all overridden
> labels (all label must be duplication of existing ones here).
> May be this solve our problem.
> -Bruno
> 2008/5/19 Adrian Crum <adrianc@hlmksw.com>:
>> Jacques Le Roux wrote:
>>> From: "Bruno Busco" <bruno.busco@gmail.com>
>>>> I think that in order to keep things simple and maintaneable we should
>>>> avoid
>>>> that a label is overwritten in two different UiLabels files to have a
>>>> different and more specific text.
>>>> If we do like this it will be an easy job to automatically check for
>>>> label
>>>> duplication.
>>> +1000, I totally agree : simple is beautiful. We don't need complexity at
>>> this level. Or someone has to explain me why...
>> A good example is the Asset Maintenance component - which reuses screens
>> from the Accounting component, but changes some terminology so that it makes
>> more sense to a maintenance person. In that case, the UI labels used in the
>> Accounting component screens are redefined in Asset Maintenance.
>> -Adrian

View raw message