Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
gtk
gtk
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,127
    • Issues 1,127
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 150
    • Merge Requests 150
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • gtkgtk
  • Issues
  • #1450

Closed
Open
Opened Nov 09, 2018 by Jakub Steiner@jimmacDeveloper

Derive HighContrast from Adwaita

Right now, HC is a completely separate 'theme'. This has historical reasons of using fullcolor icons for the main theme with low contrast.

The purpose of the HC theme is not to increase the target sizes, but to... increase contrast. The biggest issue with HC is how little testing it gets. I don't mean when designing the theme itself but apps getting tested with it. I suggest for gtk4 we:

  • Make it easier for app developers to test against HC, making it more exposed in the gtk inspector/Builder
  • Reuse 99% of Adwaita. It's about increased contrast now that we use symbolic icons, the reason to maintain a separate theme is minimal. This is what the mac does IIRC.
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/gtk#1450