Syntax highlight based on semantic information in Designer - phase 2

Currently the syntax highlight in the Designer is purely based on keywords matching on literals and regular expression matching on comments.

As we now have a semantic database, that is always up-to-date, it would be much better for the user if we could use the information from this database to enhance the visual presentation of source code.

For example display the names of constants with bold blue letters and the names of variables with light blue letters. Formal parameters could also use a different hue, to make pop more easily inside functions/altstep/testcases. etc...

Tasks:

• Fix syntax highlight in doc comments when using only the < sign, try e.g. a < b
• Refactor doc comment parser to parse comments (especially @status) in an earlier phase
  • Deprecated highlight only works on the ID after the doc comment
• Add more semantic highlight items
  • enumerated
  • class
  • unused definitions
• Improve color/style defaults, these are almost random now
• Dynamically change the example text in the preview window of the syntax coloring pref. page (currently only TTCN-3 example text is shown that is not relevant for ASN.1 and configuration editors)
• Preference to individually enable/disable semantic highlighting types