New types TerminalColor and TerminalStyle replace StyleColor and Style
to separate the meta information about styles and colors from the
user currently selected colors.
The StyleMap maps the TerminalColor/Style to the concrete fonts and
colors used in the display.
Colors are now configurable via the terminal preference page using
the new TerminalColorsFieldEditor.
All preferences are now passed in to the VT100 control so that
different terminal consumers can have different preferences and
styles.
Remove dark theme contribution. The colors of the terminal are
now inherited from the editor settings (using SystemDefaultColors)
which come from the theme. If we were to invert colors
too when in Dark theme then the colors actually end up light
background.
Change-Id: I2cf5427ac0be9a189a7f0d3565cfc97ceedb8749
Using the mouse and not the focus listeners leads to lots
of weird, unintended consequences. For example:
- If mouse does not exit the control (because, e.g. it was not
in the control) then captureKeyEvents(false) is never issued
- If mouse does leave control, then control stops capturing
events. This means that although the cursor and focus is still
on the control, keyboard shortcuts no longer go to the control,
so Ctrl-C becomes copy again. This means, depending on where you
move the mouse changes the behaviour of the control.
This reverts commit 19351cbc2b.
Change-Id: I4f57c659e21d823df049b095159a34e5c110ef29
There are two ways of specifying fonts in the terminal,
one via font definitions, and one via the font directly. The
method via the font directly was already deprecated in the public
API, this commit follows that deprecation chain through to
make it easier to identify which code paths are not likely
relevant anymore.
These methods could simply be removed as part of the major version
bump.
Change-Id: I05d746c429c4e6c3ced5ee7bb7a6172e0a255c2d
GC.getForeground / Background always create a new Color object,
so this if expression was always true.
Change-Id: Ief4ccaf1adb70967301411b012c0474608f425cb
The inconsistency of lower case and upper case in the internal
representation of the colour names made it harder than it should be
to find where colours are used in the code.
Note that the SytleMap creates lower and uppercase entries for each
colour.
Change-Id: I16b4ebe4a97adecd01f835319aa0f0d175ae3bb6
And run save actions to modernize code a bit.
Change-Id: I4a718e73e8472679aa4ead7fdefe4259004ef6d6
Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
The 4.6.0 version marks the first version of terminal built in
CDT and in a different git repo - there are no API changes.
Change-Id: Ic6c4089d7e6ccbb2701bf59fedba2b6a8dd4c856
This is applying the per-project code formatting rules that would
be applied on save in the JDT editor
See also Bug 540373
Change-Id: Id04c972c3b3cb0a6ed1ab8581185359b7cf43f91
