We have a standard setup which we use for the GDA, and something similar is used for SciSoft (as Peter indicated). The setup is committed to the repository, which is highly desirable, as it removes the dependency on how individual developers have set up their environment (and is also more likely to be "correct").

I can implement that standard setup in the dawn plugins if folks are happy for me to do so; it won't take very long, but my schedule is committed till mid-May (due to leave etc). Any other volunteers?

The problematic area is line endings. A lot of dawn files have Windows-style line endings, depending on who the last person to check in code was. It would be nice to convert everything to a standard (unix line endings), and enforce it for future commits.

Matthew

> -----Original Message-----
> From: Main mail list for the dawn collaboration [mailto:[log in to unmask]] On Behalf Of
> [log in to unmask]
> Sent: 22 March 2012 11:16
> To: [log in to unmask]
> Subject: [DAWN] Coding standards in plugins
> 
> Hi all,
> 
> I notice that the dawn plugins have minimal preferences in their .settings directory. I think it would
> be good to standardize on a set of warnings and code formatting. The scisoft plugins have, for
> example, lots of JDT settings in uk.ac.diamond.scisoft.analysis/.settings/org.eclipse.jdt.core.prefs
> 
> We also use Unix line endings and utf-8 text encoding for all source code files.
> 
> Finally, .gitignore files for plugins held in git repositories would be very handy.
> 
> Peter