Changes between Version 6 and Version 7 of CodeBestPractices

Timestamp:

2010-10-25 16:03:59 (13 years ago)

Author:

jeroens

Comment:

--

CodeBestPractices

@@ -3 +3 @@
 
 == Resources and localization ==
-Theoretically, the EwE6 scientific interface can be localized to any language, although we do not envy the poor soul commissioned to perform such a job. In intention all language-specific elements in EwE should be provided either in localizable forms or in localizable resource tables. The code is not perfect here, and please let us know if you find exceptions.
+Theoretically, the EwE6 scientific interface can be localized to any language, although we do not envy the poor soul commissioned to perform such a job. In intention all language-specific elements in EwE are provided in either localizable forms or in localizable resource tables. We have tried to consistently implement this but exceptions may exist; please let us know if you find any.
 
 The !ScientificInterfaceShared assembly offers a whack of shared resources, such as strings and images, for plug-ins and the main Scientific Interface to share to reduce the amount of scattered resources that need localizing. In your assembly simply add a statement such as import !ScientificInterfaceShared.My.Resources = !SharedResources, and access all shared resources on the imported !SharedResources thingy.
 
 When you develop your own plug-ins with a user interface, please try to stick to the following resource guidelines:
- * Reuse as many of resources provided in !ScientificInterfaceShared
- * Set the 'localizable' property of your plug-in's  forms to True
+ * Use resources provided in !ScientificInterfaceShared when possible,
+ * Set the 'localizable' property of any forms that you develop to True.
 
 == Target processor ==