Image 01
profile-image

Fuma1292

Mark Funk
Oxygen Gtk

QtCurve by HugoPereira 340 comments

Those arn't KDE applications so you can't blame KDE :).
I have found that the standalone, non-Gnome gtk theme switchers "gtk-theme-switch2" and "gtk-chtheme" have issues with some themes.

I have found the "correct" way a ~/.gtkrc must be for everything to work correctly.

non-Gnome gtk theme switchers do this:
include "/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc"
gtk-theme-name="oxygen-gtk"
gtk-icon-theme-name=""
gtk-font-name="DejaVu Sans 9"

But this doesn't work correctly with 99% of gtk themes.

You really need this:
include "/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc"
style "user-font"
{
}
widget_class "*" style "user-font"
gtk-theme-name="oxygen-gtk"
gtk-icon-theme-name=""
gtk-font-name="DejaVu Sans 9"

The font and icon parts may be able to be removed for the oxygen-gtk style because the oxygen-gtk style uses KDE's chosen fonts and icons, but I haven't tested it and this way seems to work fine for me. - Jan 13 2011
Oxygen KDE (Firefox Theme)

Various KDE 1.-4. Improvements by jimmy88 1783 comments

Minor nitpik:
The Contribute section of the Options window has a few grammar errors.

It says:
"If you appreciate my continous development on this project you could considerate a donation!"

continous should be continuous
considerate should be consider
on should be of
you need a comma after "project"

Judging by the exclamation point, you probably meant "should" instead of "could".

Revised text:
"If you appreciate my continuous development of this project, you should consider a donation!"

Of course, this sentence is still a little awkward.

Maybe you can try this:
"If you like this theme, please consider making a donation to help support its further development."

That's the end of my nitpicking. :)

Anyways, thank you for all of your hard work on this theme! - Dec 21 2010
KitchenSync

Groupware by denisq 32 comments

IMHO, this app's name is huge WIN.
KDE now has everything, including the KitchenSync. :) - Nov 08 2010
Oxygen KDE (Firefox Theme)

Various KDE 1.-4. Improvements by jimmy88 1783 comments

I just wanted to say.
Thank you for all of your work!
Your theme is the only reason why Firefox doesn't completely stand out when used with KDE. - Oct 30 2010
Oxygen KDE (Firefox Theme)

Various KDE 1.-4. Improvements by jimmy88 1783 comments

Update:
Manually exacting the xpi file in the extensions directory and deleting the existing xpi file in the extensions directory solves this problem.

You can specify this to be done automatically by firefox 4 by adding <em:unpack> to your install.rdf file

Extensions are no longer extracted by default because reading one large file is faster than reading many small ones.
This makes firefox startup faster when you have extensions/themes.

You can get more information about this, and the changes you can make to get around this, here:
https://developer.mozilla.org/en/Extensions/Updating_extensions_for_Firefox_4

Hopefully, by the time Firefox 4 is released they will be able to read/write all extension files in the XPI so <em:unpack> isn't required.


- Oct 02 2010
Oxygen KDE (Firefox Theme)

Various KDE 1.-4. Improvements by jimmy88 1783 comments

I have that "cannot write to file" problem.
After I changed the settings from "Autodetect" to a built in color scheme it starts saying "cannot read kdeglobals file..." whenever firefox starts up.
If I use the "check configuration file" button it shows the correct location of my kdeglobals file and says FOUND
The permissions of the kdeglobals file are correct (775, or Read/Write,Read/Write,Read)
I am using KDE 4.5

The Error console shows this when the color scheme chosen in the options is one of the built ins:
http://pastebin.com/z4k4urr5

In addition to the "Cannot write to file" dialog on startup and entrance to the OxygenKDEOptions dialog,
This is what it outputs if I am using the "Autodetect color scheme" option:

http://pastebin.com/frwrfJgH

I am using the latest firefox nightly
(4.0b7pre)..

You know that extensions are no longer unpacked from their xpi file in firefox 4 right?
This could be the cause of these problems

https://developer.mozilla.org/en/Extensions/Updating_extensions_for_Firefox_4

http://blog.mozilla.com/addons/2010/09/23/changes-to-how-extensions-are-installed-in-firefox-4/ - Oct 02 2010
Oxygen KDE (Firefox Theme)

Various KDE 1.-4. Improvements by jimmy88 1783 comments

I have that "cannot write to file" problem.
After I changed the settings from "Autodetect" to a built in color scheme it starts saying "cannot read kdeglobals file..." whenever firefox starts up.
If I use the "check configuration file" button it shows the correct location of my kdeglobals file and says FOUND
The permissions of the kdeglobals file are correct (775, or Read/Write,Read/Write,Read)
I am using KDE 4.5

The Error console shows this when the color scheme chosen in the options is one of the built ins:
http://pastebin.com/z4k4urr5

In addition to the "Cannot write to file" dialog on startup and entrance to the OxygenKDEOptions dialog,
This is what it outputs if I am using the "Autodetect color scheme" option:

http://pastebin.com/frwrfJgH

I am using the latest firefox nightly
(4.0b7pre)..

You know that extensions are no longer unpacked from their xpi file in firefox 4 right?
This could be the cause of these problems

https://developer.mozilla.org/en/Extensions/Updating_extensions_for_Firefox_4

http://blog.mozilla.com/addons/2010/09/23/changes-to-how-extensions-are-installed-in-firefox-4/ - Oct 02 2010
It doesn't matter what color scheme I use
buttons in GTK apps always appear white.

GIMP has another color issue:
http://img84.imageshack.us/img84/3830/gimpqtcurve.png

KDE 4.4.4

Oxygen color scheme kdeglobals:
http://pastebin.com/download.php?i=19AbLERP

kdeglobals located at $HOME/.kde4/config/kdeglobals

$HOME/.gtkrc-2.0 contains:
include "/usr/share/themes/QtCurve/gtk-2.0/gtkrc"

The option in systemsettings > Look'n'feel> colors > Options > Apply colors to non-KDE applications is unticked (the theme reverts the clearlooks if it is ticked)

I found that if I use gtk-kde4 and tick the option "Apply KDE colors to GTK applications" this problem is fixed





- Jun 27 2010
Another screenshot (this time its gtk-theme-switch2): http://img163.imageshack.us/img163/5852/buttoncolors1.png - Jun 26 2010
Why do active gtk buttons not inherit the KDE colors but instead stay white?

Screen shot of the app imagination (KDE color scheme Oxygen):
http://img571.imageshack.us/img571/8572/buttoncolors.png
- Jun 26 2010
Oxygen KDE (Firefox Theme)

Various KDE 1.-4. Improvements by jimmy88 1783 comments

Zooming in on a webpage zooms in on the scrollbars too! - Jun 04 2010
Oxygen KDE (Firefox Theme)

Various KDE 1.-4. Improvements by jimmy88 1783 comments

This is really nice.
You did a great job with this release. :)

Just a note: there are many distros that use ~/.kde4 as their configuration directory instead of ~/.kde so your color scheme autodetection doesn't work on distros that use ~/.kde4 - Jun 03 2010
KParts Plugin

Browser by fischer 139 comments

Oh, that is really cool!
Thank you for your awesome work! :) - Jun 03 2010
KParts Plugin

Browser by fischer 139 comments

My distro uses the Opensuse firefox patches which already integrate okular into firefox.

Besides Okular what else does this embed in non-KDE browsers?
- Jun 02 2010
rekonq Web Browser

Browser by adjam 290 comments

If I choose "Configure rekonq" all of the fonts are set to A. D Mono size 12 and the apply button is clickable.
This makes it imposible to change other settings without making the font look absolutely horrid.I didn't have this problem in version 4.0.
This can be reproduced if you delete/move your rekonq config file and then launch rekonq. - May 30 2010
Oxygen KDE (Firefox Theme)

Various KDE 1.-4. Improvements by jimmy88 1783 comments

The shadow on the Newtab button looks out of place.
The rounded menus look bad when the menu is over a colored background (they don't look round anymore)
I love this theme, and thanks for your awesome work!!! - May 07 2010
Glassified

Plasma Themes by painkiller101 262 comments

The shutdown dialog is unreadable when compositing is enabled because the white font blends into the background.
Although the transparent shutdown dialog looks nice, this inhibits its usability.
you should probably make the dialog solid colored when compositing is enabled like the Air and Oxygen themes do.
Also, the shutdown button in the dialog is outside of the area that encloses the words "Turn off computer"

You are enable to read the the theme name in the Plasma theme selector because the white font blends into the background.
You are only able to read it when you have clicked on it once.

This is still a great theme though.
I still use it everyday despite these small issues. - May 01 2010
Sorry, but I have to point out another thing wrong with the theme.
Try out banshee with this theme.
The selection color is a bright yellow, which makes it hard to read the text.
Change the yellow selection background to a color that isn't so bright.
The selection color (treeview) is currently
bg[ACTIVE] = "#ffff55"
bg[SELECTED] = "#ffff55"

A better color for the theme would be
#4c97e2




- Mar 18 2010
Okay I found what was wrong with the menu bar gradient.
I went to KDE system settings > Appearance > colors > options
and turned shading all the way up. (it was in the middle before).

I also fixed most of the problem with background color in gimp, but a line still remains so it is not entirely fixed yet.
To half-fix it:
The color in style "notebookbg"
and/or style "nautilus-location"
must be changed to #cccac9 - Mar 17 2010
Nice work, but I see a few things that could be improved.

You didn't change the background color in the gtkrc. Because of this, GIMP (and other gtk apps) now look...weird.

Modifying the tab pixmap doesn't affect tab spacing except in firefox (because firefox isn't a "true" gtk app). Modify the tab-overlap value in the gtkrc as well, so other apps with tabs (like GIMP) have the correct look. (modifying this setting won't affect tabs in firefox)

What resolution/size is your screen?
The new menubar pixmap looks good for small window sizes, but not bigger ones.
(this is on a 1280x720 screen, screens this resolution are usually the bare minimum nowadays )
Yes, I know that it can never be perfect, but I would hate to be the one with a screen that has a 1900x1200 resolution (these are much more common than you would think....) Because it doesn't line up so well here.

Keep up the good work!!!
- Mar 17 2010