Alloy

KDE 3.0-3.4 Themes

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

1
5.0
Description:

A neat KDE 3.x style and KWin decoration based on the Java Alloy Look&Feel from Incors (http://www.incors.com).

*Please* read the file AUTHORS for credits.

Alloy 0.4 now includes a KWin decoration thanks to Sandro Giessl.
Last changelog:

17 years ago

0.4.1a:
- Fix compile problem with QT less than 3.2 (Sandro)
- Fix compile problem with --enable-final (Sandro)

0.4.1
- Changes to the makefiles to fix some compile problems (Sandro)
- Alloyclient (Sandro):
* misc clean ups: buffering of areas which need more complex paintings
* add config dialog to configure text shadows, maximization behaviour and border thickness
- Fix incorrect text colour and gradient on menubar item mouseover
- Fix drawing of combobox arrow panel on large comboboxes.
- Added basic colour scheme

0.4
- Include Sandro Giessl's nice Kwin decoration (Thankyou Sandro!)
- Redo splitter drawing
- Separate drawing of gradients on toolbars/menubars and buttons
- Make gradient intensities user-configurable (see README)
- Add (optional) hack to use extra colours on some widgets (see README)
- Redo toolbuttons, tidy KFileDialog toolbars
- Fix crash with KToolBarWidget (as used by Konqueror)

doctorture

17 years ago

I will answer you as soon as I get into home from work!

Thanks!

Report

doctorture

17 years ago

Thanks, Sandro!
Where are you from (your names,
dbrowlees - Daniel and ceebx - Sandro)
are commom Brazilian names.


Ok, with that done, I think we can
improve it more now!!!

What do you think, for accessibility
purpose, include a configuration to
change the height of the window bar,
like the KDE2 default style.
(please check)

But we can go further. In KDE2 default
style, the buttons doesnt get
redimensioned with the window (it has
_very_ bad visual because this).
You think that is possible to adjust the
buttons height with the window bar?
This way, we can get your original
decoration incorporating all the good
things of the default XP style.
(we can use all the studies that MS
have done for our benefit).

What you think? (if you wanna help, I
can try to help you with my work)

THANKS!!!

Report

ceebx

17 years ago

I'm from germany, near munich, not sure where Daniel is from! ;-)
I like your ideas about the titlebar height but for now I won't get them done... at the moment, the whole thing is sort of optimized for fixed sizes and it would be a real pain to do that. ;-) Perhaps I will clean this up next days/weeks but I can't give any guarantee...

BTW: I will upload a new native win deco on kde-look soon you might be interested in. :-)

Report

doctorture

17 years ago

Sure, as soon as you post it I will take a look and try out!

Thanks!!!

Report

anonymous-hive

17 years ago

Sure, as soon as you post it I will take a look and try out!!!

Thanks for your effort, I hope you can get
all of this soon.

You are very helpfull! Thanks!

Report

doctorture

17 years ago

Hey, Sandro! How are you doing?

Still on it? Can I help you
with that issue of the close button
positioning?

Thanks!

Report

ceebx

17 years ago

hi,

Well, I'm confused. :)

With Alloy 0.4.1 (and the option "shrink borders for maximized windows" checked) the feature you requested works for me, doesn't it?
Now if you maximize a window, the side borders of the deco hide and the buttons can be accessed like in Win XP. Or did I get you wrong?

regards, Sandro

Report

doctorture

17 years ago

Ok, you got it!!! It is what I was
talking about.

I liked the 1 pixel configuration. For
me, it is the best configuration.

Now, Im confused with one thing.
When I use the 5 pixels configuration,
isntead of the border stretch, it shrink.
So, when I put more pixels, it does the
oposite, doesnt?
Or Im getting this wrong?

Report

ceebx

17 years ago

hey,

I hope, I understood you correctly!
The "shrink borders for maximized windows" and the "border size" settings are two different things. While the first one just optionally does the "WinXP behaviour" for maximized windows, thus making buttons etc. more easily accessible (independent of the pixel settings), with the border size setting it is possible to change the borders' thickness for non-maximized (or with the shrinking option disabled for all) window states.

Report

doctorture

17 years ago

Thanks!!!
I noticed what that configuration (border
sizes) does. But I think it wouldnt work
that way when the window is maximized,
because it is 'eating' the rightmost part of
the window.
It is possible implement it in a way it doesnt
hide the right side of the window when it is
maximized?
Did you understand me? (try to maximize a window and change the border size).

Thanks for your attention!

Report

doctorture

17 years ago

Hey, I will install this new version now and I will give you a feedback!

Thanks again!!!!

Report

ajacoutot

17 years ago

Hi !

great style :)
What color-sheme are you using in those screenshots ? It looks great.
Thanks...

Report

C

dbrownlees

17 years ago

~/.kde/share/apps/kdisplay/color-schemes/Alloy.kcsrc:
[Color Scheme]
Name=Alloy
activeBackground=51,91,146
activeBlend=118,162,223
activeForeground=255,255,255
activeTitleBtnBg=238,238,230
alternateBackground=238,246,255
background=241,240,227
buttonBackground=241,240,227
buttonForeground=0,0,0
contrast=7
foreground=0,0,0
inactiveBackground=230,226,213
inactiveBlend=222,218,213
inactiveForeground=143,143,143
inactiveTitleBtnBg=238,238,230
linkColor=0,0,192
selectBackground=249,224,137
selectForeground=0,0,0
visitedLinkColor=128,0,128
windowBackground=255,255,255
windowForeground=0,0,0

and ~/.qt/alloystylerc:
[Settings]
primaryColor=#93add1

Report

ajacoutot

17 years ago

excellent, thanks :)

Report

kaishu

17 years ago

This is one of the best contributions ever made to kde-look. Thank you all.

Report

ushohet

17 years ago

Awesome theme! I use it since 0.1 and I it just gets better with every new release!
Big thanks to Sandro - keep it up!

Report

pippi

17 years ago

Hej!

Wow and thank you, this is soo nice, i use it and am very impressed and satisfied. This style has all i want!

Thanks ;)

Pippi from Sweden

Report

nbensa

17 years ago

How can this theme be the default in KDE?

I mean, Keramik is nice, but Alloy is by far more beatiful and clear. We need to tell kde's devs to drop Keramik and adopt Alloy :-)

Norberto

Report

hbbio

17 years ago

Keramik is even not nice. It was 2001-style-hype, and is already looking old - and amateurish.
I used Light3, before switching to Alloy. Let's make it default... now !
Just one comment: maybe the tabs should be modified a bit, so that the first one is "aligned".

Report

Richardve

17 years ago

Could you please comment out the following lines in alloy.cpp for the next version? big thanks! :)

line 725 to 742.

(it's not there in the original Alloy theme either, and splitter bevels are ugly)

Report

tvon

17 years ago

Howdy,

I've been getting konq crashes using this style. This happens on two occasions: when the popup window opens on loading http://www.washingtonpost.com/ and when I have konq open and switch from another style to kalloy. This has been happening for all versions of kallow (1-3).

Here is the washingtonpost.com traceback, I'll post the other traceback when it happens again:

(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 28846)]

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x40efd971 in waitpid ()
from /lib/libpthread.so.0
#0 0x40efd971 in waitpid () from /lib/libpthread.so.0
#1 0x40660a59 in KCrash::defaultCrashHandler(int) ()
from /usr/kde/3.1/lib/libkdecore.so.4
#2 0x40efc7bd in __pthread_sighandler () from /lib/libpthread.so.0
#3
#4 0x40a17374 in QWidget::colorGroup() const ()
from /usr/qt/3/lib/libqt-mt.so.3
#5 0x40746f9c in Alloy::eventFilter(QObject*, QEvent*) ()
from /usr/lib/kde3/plugins/styles/alloy.so
#6 0x409e7e8a in QObject::activate_filters(QEvent*) ()
from /usr/qt/3/lib/libqt-mt.so.3
#7 0x409e7dae in QObject::event(QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3
#8 0x40a19cb2 in QWidget::event(QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3
#9 0x409909a1 in QApplication::internalNotify(QObject*, QEvent*) ()
from /usr/qt/3/lib/libqt-mt.so.3
#10 0x4098ff79 in QApplication::notify(QObject*, QEvent*) ()
from /usr/qt/3/lib/libqt-mt.so.3
#11 0x405dc57a in KApplication::notify(QObject*, QEvent*) ()
from /usr/kde/3.1/lib/libkdecore.so.4
#12 0x4093d82c in QETWidget::translatePaintEvent(_XEvent const*) ()
from /usr/qt/3/lib/libqt-mt.so.3
#13 0x40939262 in QApplication::x11ProcessEvent(_XEvent*) ()
from /usr/qt/3/lib/libqt-mt.so.3
#14 0x4094ce7d in QEventLoop::processEvents(unsigned) ()
from /usr/qt/3/lib/libqt-mt.so.3
#15 0x409a31bf in QEventLoop::enterLoop() () from /usr/qt/3/lib/libqt-mt.so.3
#16 0x409a3074 in QEventLoop::exec() () from /usr/qt/3/lib/libqt-mt.so.3
#17 0x40990bc0 in QApplication::exec() () from /usr/qt/3/lib/libqt-mt.so.3
#18 0x41422602 in main () from /usr/kde/3.1/lib/konqueror.so
#19 0x0804cf0a in strcpy ()
#20 0x0804e6a3 in strcpy ()
#21 0x0804d991 in strcpy ()
#22 0x0804be08 in strcpy ()
#23 0x410687ab in __libc_start_main () from /lib/libc.so.6

Report

C

dbrownlees

17 years ago

What versions of QT/KDE have you got? If you have QT earlier than 3.1.1, could you please try upgrading QT?

If that doesn't work, then could you please compile Alloy with debugging enabled (--enable-debug=full) so the backtrace is a bit more useful. If you're up to compiling QT with debugging on too, that would be even better.

Has anyone else seen this?

Report

tvon

17 years ago

qt: 3.1.2
kde: 3.1

Dist is gentoo, everything is current as of...2 weeks ago.

Report

C

dbrownlees

17 years ago

Hmm, does it still crash if you remove the "Location:" label from konq's location bar? (Use Settings/Configure Toolbars)

Could you also try changing lines 1905 & 1909 (alloy 0.3) from
painter.setPen(toolbar->colorGroup().mid());
to
painter.setPen(parent->colorGroup().mid());

If that doesn't fix it, then it's probably easier to continue via email - dbrownlees at paradise.net.nz if possible.

Report

C

dbrownlees

17 years ago

Ok, after browsing around www.washingtonpost.com for a while I finally managed to reproduce the crash. As far as I can tell, the fix that I detailed above (change toolbar to parent) seems to solve the problem.

tvon, can you confirm this?

Report

17 years ago

0.4.1a:
- Fix compile problem with QT less than 3.2 (Sandro)
- Fix compile problem with --enable-final (Sandro)

0.4.1
- Changes to the makefiles to fix some compile problems (Sandro)
- Alloyclient (Sandro):
* misc clean ups: buffering of areas which need more complex paintings
* add config dialog to configure text shadows, maximization behaviour and border thickness
- Fix incorrect text colour and gradient on menubar item mouseover
- Fix drawing of combobox arrow panel on large comboboxes.
- Added basic colour scheme

0.4
- Include Sandro Giessl's nice Kwin decoration (Thankyou Sandro!)
- Redo splitter drawing
- Separate drawing of gradients on toolbars/menubars and buttons
- Make gradient intensities user-configurable (see README)
- Add (optional) hack to use extra colours on some widgets (see README)
- Redo toolbuttons, tidy KFileDialog toolbars
- Fix crash with KToolBarWidget (as used by Konqueror)

12345678910
Be the first to comment
rvc-2011
Apr 28 2013
File (click to download) Version Description Downloads Date Filesize DL OCS-Install MD5SUM
*Needs pling-store or ocs-url to install things
Pling
0 Affiliates
Details
license
version
updated Jul 30 2003
added May 26 2003
downloads 24h
0
mediaviews 24h 0
pageviews 24h 1