We should explore that a bit more. Just like Maven support or some properties (and Log4J 2 integration;-) I added to this Strava (fit band data syndication portal) client fork: https://github.com/keilw/JStrava/blob/master/src/test/resources/testconfig.properties.template I am not even sure, if the patch file has to be in repo at all. A "template" and the current file is barely more than that could be checked in, but filling stuff in especially screen resolution should be left to users.
Werner On Wed, Sep 10, 2014 at 6:30 PM, eberhard speer jr. <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > So, if I understand you both correctly the idea is to put the > 'defaults' -- not just desktop I presume -- in the patch file as an > "abstract" parent for which the User can, if they so decide, change > the given 'best' guesses. > > That sounds like a good solution to me, provided the DeviceMapClient > has the option to ignore the 'defaults'-patch and all the 'defaults' > go to the abstract parent in the patch. > > If that's the case, I'm all for that ! > No defaults if you don't load the patch, given or your defaults if you > do load the patch. Great ! > > esjr > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (MingW32) > > iQEcBAEBAgAGBQJUEHyZAAoJEOxywXcFLKYcD2wIAMNDGPEJl3ZqYCGse/HKkYXI > c6uaqwGLAbcEF6a4Ue+cIett+HbIyuyb3Qz7sfmAJOsMJll5u2Tn01JdTo8Bmx/5 > AVA0MlBQVsffRpzEACCpBxNiljGnBjyS5n857okuDd5tBrUcVpdK23P0jGyTXPq2 > mNStygSRSfFAZvQ/SVf6r48mEW4xysujTKLLOn+alsISeuJ54BrviCeQxQGnkUOi > 3h/rIaxKm/mbhdIZy77fXEM4m8lTgIMaGSH3NDjqdz8I21oM9EqvzrS0iNNoFpf4 > bh0LXMm0b0CgCirGXmjq5Mt/2Se14naOokjvMDhjPVszIUtsV+HnIn0/TrB41HA= > =y2f8 > -----END PGP SIGNATURE----- >
