Configuration presets

[GoogleCodeExporter]

What steps will reproduce the problem?
1. setup: checkout, build
2. configure
3. run
4. if next project and different language 2

What is the expected output? What do you see instead?

 Would like to have predefined configuration presets (java, c, ...).
 Those presets to be merged, in case you want to visualize history of
repository with multiple languages used.

What version of the product are you using? On what operating system?

 Todays trunk.

Please provide any additional information below.

 It would make user experience in configuration step much friendlier.

 Preset:
  - Configuration settings referenced from projects configuration by name.
  - Contains information about patter to color mapping, engine and
configuration flags.
  - Since file-color mappings are defined by regular expressions, list of
colors can be easy merged.
  - To avoid conflicts in setting like engine used, I suggest to:
    -divide presets into categories that names would reflect configuration
area,
    -or warn user about conflicting setting and emulate map behavior, last
write wins.

 Two types of presets.
  - Predefined presets:
    -define file-colors mappings for common file sets,
    -define rendering settings.
  - User presets, whatever user wishes to have.

 Reference to preset could be similar to InputFile.

Original issue reported on code.google.com by hubert.iwaniuk on 6 Aug 2008 at 8:12

[GoogleCodeExporter]

This is enhancement not defect.

Original comment by hubert.iwaniuk on 6 Aug 2008 at 8:13

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

That would be cool.

Original comment by felipe.contreras on 30 Aug 2008 at 11:29