Friday, February 20, 2009

Arora 0.5 and Oxygen Style



Tonight I tagged Arora 0.5. And with every release starts development on the next release. One of the things I would like to improve for 0.6 is integration with KDE4. To help do that I have started a wiki page of KDE4 items. When using Arora on KDE a bunch of the first issues everyone runs into are really just improvements that need to be made to the Oxygen style. Little things like returning the KDE icons for back/forward, returning the correct size check boxes in QtWebkit, and supporting the new QTabBar style hints in Qt 4.5 will really help Arora fit in better with KDE 4. Of course these fixes will benefit everyone who uses QtWebKit in their application and anyone KDE application that uses the new QTabBar features. So I am putting out a request for help. If you happen to have your box all setup for KDE development and have a few minutes to spare helping making Oxygen an even better style would be most appreciated.

14 comments:

kev009 said...

That bear icon looks rather conspicuous...

Benjamin Meyer said...

Yah I asked for a Polar Bear combined with a planet icon. He is suppose to be sleeping. Later on we realized what people could see :) If anyone want to make a better one the original svg is in the repository.

Will said...

How about Bespin? Oxygen isn't really the users' choice. It's the devs' choice because Bespin is too much OS X-like to them... You should know that most of the forks of KDE 4 themes are based on Bespin...

Mark said...

@Will: Spreading FUD won't make Bespin any better. If you looked at its code you would maybe understand the real reasons behind KDE's decision.

--
Mark Kretschmann

Dread Knight said...

It's really nice to hear about KDE4 integration for Arora, KDE really needs to webkit open source browsers. GTK has rather too many webbrowsers already and besides that, google's chrome devs are fools and pick the garbage GTK (i like GTK and gnome but i think that stuff really needs to be killed in favor to QT and KDE and just have things less buggy and more polished overall.. if a distro will provide multiple interface setups and skins out of the box, i don't think average people will give a fuck about backends).


Bespin is nice, but it's configuration dialog is so confusing and shitty... and rather not integrated well into KDE atm. Hope they'll sort out that stuff soon.


Cheers and keep showing arora some love, because konqueror is next to useless for me... i can't get google docs working.. not even with the (early) webkit plugin atm.. heh

jensbw said...

Hi Ben:
I moved the icon loading code to QCommonStyle, precicely to allow Oxygen to pick up the icons without modification. Let me know if it's not working in the latest Qt 4.5 snapshots as it certainly does on my system. There was also a bug where it would fall back to Crystal SVG instead of the oxygen icon theme when the theme was not explicitly set in KDE. In other words the icon issue _should_ already be addressed. The QtIconLoader i blogged about recently is of course another option and doesn't add any dependencies to the project.

Jens

Will said...

"If you looked at its code you would maybe understand the real reasons behind KDE's decision."

@Mark: Would mind enlightening me up?

Eike said...

@Will: Bespin has a rather convoluted codebase that makes it hard to maintain or contribute to for anyone but its original author. It also uses a lot of X APIs directly rather than use Qt's painting APIs, which means it has portability issues (yes, many KDE-on-Windows users actually prefer using Oxygen to the native style, and there are also other platforms without X that we might want to use Oxygen on, such as framebuffer-based mobile platforms). It also suffers from various rendering and design glitches and inconsistencies and overall quality problems.

During the time that Bespin was still the original Oxygen codebase, efforts were of course made to address both the technological and artistic problems, but eventually the creative differences, if you wish, proved to be an impenetrable problem and the relationship between the KDE Artists/Oxygen team and the Bespin author thus ended.

Today's Oxygen codebase is very clean and maintainable, portable, and overall a great base for future development and enhancement.

Johannes (litb) said...

Contrary to one commenter in here, i think that QtCurve is the best theme out there (with the "Silk" QtCurve style). It looks so clean... But i guess its code base is also not quite nice... I looked into it one time and it contains quite many special cases for firefox, open office and whatnot. not nice...

But i just love its look and its great performance. Oxygen just sucks in terms of performance. it's utterly slow

pvandewyngaerde said...

GTK is deprecated, use QT !

Mamarok said...

@Johannes: you are joking, right? Who on earth would want to have KDE apps look like GTK...

Paul said...

I use arora all the time unless I need flash (I know I can use the qt 4.5 snapshot, but kde 4.2 doesn't behave well under it, and I have also tried a build of arora 'statically' linked to 4.5 .. this works, but I cant use the theme of my choice).

Anyway, I hope that you guys keep Arora simple as it is. The only thing I guess Id blike to see if the layout of menus a la KDE as well as use of KDE file dialog boxes (the standard qt ones just try to look like Windows too much)..

May qt 4.5 be soon released and may KDE 4.3 fix the issues it has with it and i will never have to use a gtk browser ever again. !! ;)

Will said...

@Eike
Then maybe Oxygen team should help Bespin team to improve it? No matter how clean the Oxygen's code base is, more and more people will still use it because it's just outright beautiful and it supports global-menubar...

Will said...

@Eike: I meant Bespin...

Popular Posts