After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 731624 - Include Adwaita theming
Include Adwaita theming
Status: RESOLVED FIXED
Product: gedit
Classification: Applications
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2014-06-13 16:27 UTC by Matthias Clasen
Modified: 2014-08-10 15:03 UTC
See Also:
GNOME target: 3.14
GNOME version: ---


Attachments
Include Adwaita theming (8.17 KB, patch)
2014-06-13 16:27 UTC, Matthias Clasen
committed Details | Review

Description Matthias Clasen 2014-06-13 16:27:12 UTC
With Adwaita moving into GTK+, the application-specific pieces
of the theme have to live with the applications themselves.
Comment 1 Matthias Clasen 2014-06-13 16:27:21 UTC
Created attachment 278421 [details] [review]
Include Adwaita theming
Comment 2 Paolo Borelli 2014-06-13 17:09:38 UTC
Review of attachment 278421 [details] [review]:

as discussed on irc the patch looks good to me.

Benjamin does not like this plan very much... on the other hand he does not seem to like any of the plans :P

Unless we decide otherwise at the gnome-wide level, feel free to push it
Comment 3 Ignacio Casal Quinteiro (nacho) 2014-06-14 07:56:31 UTC
Review of attachment 278421 [details] [review]:

should we merge the other css we have into this one?
Comment 4 Paolo Borelli 2014-06-14 08:22:49 UTC
(In reply to comment #3)
> Review of attachment 278421 [details] [review]:
> 
> should we merge the other css we have into this one?

No, I think we need the theme-specific part and the generic part separate: over time I would not mind contributions for other themes (in particular gedit.highcontrast.css or gedit.win32.css or similar)
Comment 5 Benjamin Otte (Company) 2014-06-16 13:25:13 UTC
(In reply to comment #2)
> Benjamin does not like this plan very much... on the other hand he does not
> seem to like any of the plans :P

I think this approach is fundamentally wrong because it encourages thinking of Adwaita as an API.

The correct fix is to (a) not need custom CSS or (b) put app-specific CSS into the theme.

There is no reason why Adwaita cannot have app-specific CSS. Moving files between repositories doesn't change that.
Comment 6 Matthias Clasen 2014-06-16 17:03:38 UTC
Then let state just as categorically that putting app-specific stuff into the theme is fundamentally wrong. It means that as the number of apps grows the size of the theme tends toward infinity, and every app loads all other the apps' specific theming.
Comment 7 Benjamin Otte (Company) 2014-06-16 18:04:11 UTC
Putting theme-specifc CSS in the app is equally wrong, if not more so. It means that as the number of themes grows the amount of CSS tends towards infinity, and every app needs to maintain every themes' specific theming.
Comment 8 Paolo Borelli 2014-06-21 11:51:53 UTC
We all know that there are pros and cons to both approaches and that there is no perfect solution. However the "many apps, few themes" scenario seems much more pressing than the "many themes" one.

Beside, no one forbids authors of $awesometheme to also include app specific styling like it is done today.


I'd say for the time being the patch should go in, though it is pretty bad to have to do this manually instead of just dropping a resource in the binary with proper naming conventions


What about the the a11y themes?
Comment 9 Matthias Clasen 2014-07-10 12:33:02 UTC
See bug 732959 for discusssion of 'load from resource automatically'. For now, I'm going to push this patch
Comment 10 Matthias Clasen 2014-07-10 12:33:27 UTC
Attachment 278421 [details] pushed as cec4be8 - Include Adwaita theming