#45 Store overridden prefs in separate file

[Eivind Tagseth]

As others have reported (bug 662939), it can be quite
confusing how the preferences file gets really large,
and you have no easy way of knowing which of the
preferences you have overridden. It's also annoying
version control wise, since your version control
software always thinks it has changed.

Here's a simple patch that lets the user create a
NAME-custom-prefs.propertes file in addition to the one
generated by middlegen. Middlegen will load this file
after it's own, thus overriding any already set properties.

Now you can put NAME-prefs.propertes in your
.cvsignore, and just maintain
NAME-custom-prefs.properties in cvs.

The patch is against cvs HEAD.

Eivind

[Eivind Tagseth]

custom_properties.patch