The names that followed the 'extends' and 'implements' keywords were not
properly colored. Two new syntax have been added to deal with that case.
Note: Only one could have done the job.
It corrects some bugs or omissions that occured in the Java syntax.
Plus, it adds some new stuff like the highlight of enum classes when
decalred or the arrow operator '->'.
In some case, the highlight of some generic types was overflowing:
public void method(List<String> strings, List<Integer> integers) {}
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
overflow of the first parameter
It corrects this behavior by restraining the type highlight before the
parameter name.
Up to now the following text 'new ArrayList<>()' was not highlighted
correctly. The modification that has been done highlights it like a
normal type name.
Methods are colored in green, types in yellows and annotations in
orange. Some italic flavours are also used.
The most difficult thing to achieve was to highlight constantly Java
types or classe names.
The Java syntax is located under the ./after/syntax repository.
The syntax provides mainly rules for methods, types and annotations. All
syntax rules have the prefix 'javaOdyssey'.
A new function s:l has been introduced in order to use 'highlight link'
instead of just a 'highlight' which redefined a new highlight instead of
using an existing one.
This function is used in some case in order not to redefine an
highlight. Now, Function links to Identifier and StorageClass, Structure
and Typedef all link to Statement.
The highlight group named 'Operator' is colored with the procedure
color.
Plus, the highlight groups named 'StorageClass', 'Structure' and
'Typedef' are colored with the keyword color.
A last minute change before the new release: Types are back to having no
attribute.
In fact, it is expected to set all the attributes in the next release
(0.4.0), so we don't want to go head of ourselves.
The 'Syntax' section is renamed 'Default Syntax'.
Then, if a language or a plugin is supported, its associated section
will be named '<language or plugin> Syntax'.
A script-scoped variable containing all the different attributes has
been initialized.
This variable is a list with the attibutes for the terminals and the
GUIs.
The colors related to the errors, the warnings and the types have been
changed.
- Hue of the red (errors): 10
- Hue of the orange (warnings): 40
- Hue of the yellow (types): 80
The following colors have been modified:
- type: The color of the types is now very yellowish, and its hue is 70.
- keyword: The color of the keywords is now a blue a little bit darker
whose hue is 180. It is great because it is nearer the hue of
the background color.
- constant: The color of the constants is now a dark blue instead of a
yellow-green.
The RGB values of the GUI colors are now taken in input to compute the
value of the Xterm colors by using an approximation.
Now, in order to chose colors for the GUI or the TERM, it is enough to
only provide the HSB triplet.
The function named s:hsv2hex has been separated into two functions named
respectively s:hsv2rgb and s:rgb2hex.
The function that helps now populating the s:color array is named
s:colorize.
The are now two Utility sections:
- Color Utility: Part of the script that helps defining colors.
- Highlight Utility: Part of the script that helps defining highlights.
In some terminals, a color of cursor disappeared when it was on a
parenthese. This modification seems to solve the problem given that the
cursor turns orange and the matching parenthese is underlined in orange.
The variable s:colors is now a dictionary that maps the keys 'gui' and
'term' to their associated value. In one case, it is an hexadecimal
string and, in the other, it is a number between 0 and 255.
The true color and its 8-bit association are managed in the same tuples.
In other words, s:colors is now an array of tuples.
Rigth now, I think the mapping between the true and the 8-bit colors can
be improved. I have just used an approximation script I found on the
internet (URL too long).
The two groups were ToolbarLine and ToolbarButton. I spent some time
trying what those are until I found 'WinBar' (Not sure I figure
everything out right now).
The .gitignore file was only containing the line '*.swp', which are
files related to Vim. Given that it focuses to much on a given editor
and not on files or repertories of the project, the line has been
removed.
In the same time, the entire file is also removed given that it is
empty.
A code snippet demonstrating how to use the color scheme was missing. It
has been added under the section that describes how to configure the
color scheme for terminals.
The Changelog.md contains the feature of the first releases. Basically,
it just states out the required configuration to use the color scheme,
and the colors that are used.
The initialisation step consists in cleaning the highlights and the
syntax from previous schemes, and setting the background accordingly.
Plus, the variables used within the script are also initialized.
It must be noted that the colorscheme is only defined for the GUI and
for versions of Vim that has the 'termguicolors' option set. In addition
the version must be greater than '580'.
The colors of the scrollbar and its thumb which are both associated to
the Pmenu have been modified after using it on an example.
The scrollbar has now the same color as the main part of the PMenu, and
the color of its thumb is the one of the 'linenumber'.
The README.md contains the instructions to install Odyssey as a Vim
plugins. The other sections may not have that much importance (simple
introduction and license section).
Almost all the default highligting groups have been added. Those which
remain commented are related to the GUI, and they will be added later.
The color of some of the already existing groups has changed, but it has
not been logged because nothing is fixed right now.
The function s:HL has also been change a little bit in order to support
an optional third argument to provide the value of 'gui'.
It adds/rewrites colors to some default highlights groups like ErrorMsg
or WarningMsg or Title. The intention is to cover all the default groups
before, maybe, trying to cover 'filetype' related groups.
It must be noted that the color named error and warning are used in the
interface, but, only to put the emphasize on warning or error messages.
All the default highlight groups are present, but, now, most of them are
commented.
Each time a decision is made on what color should be used, the
corresponding groups will be uncommented.
Firstly, an error has been corrected in the utility function named
hsv2rgb.
Secondly, some of the more useful highlight groups have been processed,
but everything may still change.
The Odyssey colorscheme is based on a 12-color palette, and the main
ambiance is represented by a dark shade of green whose origins come from
the light sea green color.
Two new helper functions have added to help in the setup of the
colorscheme.
- hsv2rgb: This 1st function generate the RGB hexadecimal string
associated to a color given its HSV triplet.
- HL: This 2nd function is a wrapper for the 'highlight' command.
Ludovic Koenig