Vimix and Vimix-Dark marco/metacity theme title offcenter and fix

Giskard

Hi! I made a quick fix for an issue that was annoying me: the titlebar of Vimix and Vimix-Dark themes is too tall, and the title appears unaligned with the buttons.
This issue is not present in the Vimix-Light theme.

So I edited the metacity xml files to fix the padding and the result is this

metacity-theme-1.xml: https://drive.proton.me/urls/RRCB4VMG8C#4XrkjohmQJup
metacity-theme-2.xml: https://drive.proton.me/urls/S1M4F66RG4#CjSuXoCcO6Dr
metacity-theme-3.xml: https://drive.proton.me/urls/NRK3HK268W#obyl8AAyvv4C

The name tag inside info, should be changed from Vimix-fix to Vimix when copied inside the metacity-1 directory of Vimix theme, and to Vimix-Dark for the Vimix-Dark theme.

vimanuelt

Giskard
To contribute this fix to the correct project, follow these steps:

Identify the official project repository:
The Vimix GTK theme is hosted here: https://github.com/vinceliuice/vimix-gtk-themes
Fork the repository on GitHub:
Go to the link above and click “Fork” in the top-right corner to create a copy of the repository under your GitHub account.

Clone the fork locally:

git clone https://github.com/YOUR_USERNAME/vimix-gtk-themes.git
cd vimix-gtk-themes

Create a new branch for the fix: git checkout -b fix-metacity-padding
Replace or patch the relevant metacity-theme-*.xml files in the appropriate theme directories (Vimix, Vimix-Dark).
Update the info name tag in each XML file to reflect the correct theme name as explained (e.g., Vimix, Vimix-Dark).

Commit the changes:

git add .
git commit -m "Fix Metacity titlebar padding and alignment for Vimix and Vimix-Dark themes"

Push the changes to the fork: git push origin fix-metacity-padding
Create a pull request:
Visit the original repository and GitHub will prompt to "Compare & pull request". Click it, write a clear summary, and submit the PR.
Optional: Mention that the fix does not apply to Vimix-Light, and include before/after screenshots for clarity.

Giskard

vimanuelt Is GhostBSD using this repository for its Vimix theme package?
I'm asking because what I see inside the repo is different. There are more variants and the default icon theme, cursor theme, panel colors and checkbox/radiobuttons colos are different.
Is GhostBSD is using a customized fork of it?

In any case, I'll do a pull request in the upstream repository. Just tell me if I should do the same to the GhostBSD theme repository, if there is one.

vimanuelt

Giskard
I noticed that the Vimix theme included in GhostBSD differs from the upstream repository as there are additional variants, different default icon and cursor themes, and modifications to panel colors and widget styling. This suggests GhostBSD is maintaining a customized fork.

Rather than maintaining a separate version, I’d recommend contributing these improvements directly to the upstream Vimix repository. Upstreaming the changes would simplify maintenance for GhostBSD and ensure visual consistency across systems.

If upstream accepts them, GhostBSD could drop the custom fork entirely and use the official version instead. That way, your improvements benefit the broader community and reduce duplication of effort.

Giskard

That's my pull request: vinceliuice/Vimix-gtk-themes277
There's another issue with the panel background in the upstream themes, which is not present in the fork used by GhostBSD. For this I wasn't able to create a correct fix, but only a workaround, so I just opened an issue vinceliuice/Vimix-gtk-themes278

If the GhostBSD mantainers wants my fixed versions of the themes, here are the downloads: https://drive.proton.me/urls/SSKVSMZYK8#jxZuxH06kgy7

Vimix-fix and Vimix-Dark-fix: GhostBSD versions with fixed titlebar
Vimix*Doder and Vimix*Grey: Two of the upstream themes with fixed titlebar and panel

Edit 2024-05-02: I just modified the panel background of the Vimix*Doder and Vimix*Grey themes to be translucent like in the default GhostBSD themes. In that way, they can be used as replacements for the default themes.

PS. I don't know if the upstream themes are maintained anymore. The last release is from 1 year ago.

Edit: 2024-05-03: I created an issue as enhancement in the GhostBSD issue tracker: ghostbsd/issues256