| best pratice on where to store property strings? [message #576305] |
Mon, 25 August 2003 00:55 |
 Dave Carlson
Messages: 34
Registered: July 2009 |
Member |
|
|
A recent message from Ed Merks contained a comment about property message
strings, which raises a question for me. The comment:
-------------------
All the error messages are in plugins/org.eclipse.xsd/plugin.properties.
They typically have names based on keys in the spec's html, e.g., the
message:
cvc-complex-type.3 = The attribute ''{0}'' is not permitted
-------------------
It seems that EMF plugins keep all translation strings in the
plugin.properties file, whereas the Wizard generated plugins from non-EMF
always specify a separate resource file for properties. Outside of EMF and
XSD, the plugin.properties is only used for variable replacement in the
plugin.xsd definitions. Other plugins as part of Eclipse core contain
several properties files that are distributed across different packages
within the plugin (the JDT plugin comes to mind here).
I'm looking for a best practice (or at least a common convention for my own
code) about where to keep message properties. Any reason not to centralize
all property strings in the plugin.properties files as done with EMF?
Thanks!
Dave Carlson
|
|
|
Powered by
FUDForum. Page generated in 0.01423 seconds
Search
Help
Register
Login
Home
