GTK Theme Maker

Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net

Available as/for: -

Description:

Notes:

Be sure to set the Gtk theme to "Raleigh" with the Gnome Tweak The preview frame will not show the theme in the text editor until you edit it.
There is about a 5 second delay before the theme appears.

Known Problems:

All widgets are not affected by the theme.

This program has been created and tested on Fedora 15.

If you would like to help develop GTK Theme Maker, please join this group:
http://opendesktop.org/groups/?id=377

Last changelog:

9 years ago

0.9.0.0:
First Release! Program is not functional yet.

0.9.0.1:
Fixed Bug that caused widgets not to be affected by theme engine changes
Split window UI file and preview UI file

8 comments
Comments/Ratings

Please login or register to add a comment or rating

omerfeyyaz
3 years ago

Nice but I think it should be a hungry button if it comes with the ability to organize the theme we choose.

Report

user333
9 years ago

There seems to be a BIG bug in the program... theme engine settings do not affect anything, only the colors change. I guess I'll have to find a way to set the theme another way. Do any of you know how to do this? I used to know how (in GTK2) but I'm not sure about GTK3.

Report

Padster
9 years ago

You mean the "gtk.css"? It seems GTK3 themes are in different files. So far I've seen "gtk-widgets.css" as the main file, but I've also seen the widgets each spread out into their own files. Could you somehow load all the *.css files in the specified folder, in separate tabs, perhaps?

Report

user333
9 years ago

Yes, I am planning to support multiple files. What do you think of having each widget type in a separate file? I've seen some GTK3 themes done like that, and it makes things really easy to edit. I would add a drop-down menu where you could select the widget type, and a text editor would show only that widget's section. This would solve a lot of technical problems if I did it this way. Even though there wouldn't be a GUI for editing themes, CSS isn't that hard to learn. I am planning to implement one in the future but for now I don't want to mess with a CSS parser(something that would be critical in order to open up files, but with a text box I don't need it).

By the way, I found a solution to the bug I mentioned. With a little work the theming engine settings will work properly, and I'll update it as soon as I can get the code done. (I've posted two other messages saying this, but for some odd reason they didn't show up)

Report

Padster
9 years ago

Sounds good to me.

Report

Padster
9 years ago

It's awesome that we're finally seeing something come out of this, even if it's still heavily under development!

But, yes, I can see how it needs some work, as the menus and sliders, etc aren't working. But this is encouraging :)

Report

user333
9 years ago

It seems you discovered the other problem I didn't mention ;) I borrowed the widget set from TWL's glade file and didn't "declare" the widgets in the Python code, so the widgets don't actually work yet.

Report

Padster
9 years ago

Ah, okay.

Report

9 years ago

0.9.0.0:
First Release! Program is not functional yet.

0.9.0.1:
Fixed Bug that caused widgets not to be affected by theme engine changes
Split window UI file and preview UI file