[
https://issues.apache.org/jira/browse/OFBIZ-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545219
]
Jacques Le Roux commented on OFBIZ-1425:
----------------------------------------
I wonder if it's not too sophisticated notably I don't like much the idea of
several sources of informations. On the other hand, I agree that this strategy
fulfill all needs already expressed
To summarize
+1 for FieldDescription.[fieldname] - will be used for all fields of that name
+1 for FieldDescription.[entityname].[fieldname] - will be used for the
specific entity field
0 for Convert the field name into a sentence, then return the sentence
+1 for localisation, (hope we are all ambitious developpers if we really want
to increase our market share ;o)
-1 to use the <description> outside of the scope of the entitydef file (only
used by.for programmers)
Do we really need to add <default-resource-name> in entity ? Each entity and
view-entity has a package-name and we could use it there to find related
properties file. As, if I remember well, package-name is not mandatory I
quickly checked and it seems to be well used.
My 2 cents
> Improve the ModelField.getDescription method
> --------------------------------------------
>
> Key: OFBIZ-1425
> URL: https://issues.apache.org/jira/browse/OFBIZ-1425
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Reporter: Adrian Crum
> Priority: Minor
> Attachments: example.patch, modelfield.patch
>
>
> Based upon discussion on the dev mailing list and in the OFBIZ-1387 issue,
> modify the ModelField.getDescription method so it uses a more comprehensive
> way to resolve a field description.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
