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)

tvon

17 years ago

I tried building kalloy with debugging but there seems to be no extra information....I used ebuilds before, I'll do it manually next...

While I'm here, this is the "konq crashes when switching from one style to kalloy" output:

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

(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 0x40746ffc 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 0x40967cd9 in QWidget::repaint(QRegion const&, bool) ()
from /usr/qt/3/lib/libqt-mt.so.3
#13 0x4099175b in QApplication::sendPostedEvents(QObject*, int) ()
from /usr/qt/3/lib/libqt-mt.so.3
#14 0x4099159c in QApplication::sendPostedEvents() ()
from /usr/qt/3/lib/libqt-mt.so.3
#15 0x4094cdce in QEventLoop::processEvents(unsigned) ()
from /usr/qt/3/lib/libqt-mt.so.3
#16 0x409a31bf in QEventLoop::enterLoop() () from /usr/qt/3/lib/libqt-mt.so.3
#17 0x409a3074 in QEventLoop::exec() () from /usr/qt/3/lib/libqt-mt.so.3
#18 0x40990bc0 in QApplication::exec() () from /usr/qt/3/lib/libqt-mt.so.3
#19 0x41421602 in main () from /usr/kde/3.1/lib/konqueror.so
#20 0x0804cf0a in strcpy ()
#21 0x0804e6a3 in strcpy ()
#22 0x0804d991 in strcpy ()
#23 0x0804be08 in strcpy ()
#24 0x410697ab in __libc_start_main () from /lib/libc.so.6

Report

HeimirFreyr

17 years ago

Which Window Decoration is used in the Alloy screenshot? It looks pretty neat.

Report

HeimirFreyr

17 years ago

Found it. Turns out to be the new Glow.

Report

mononoke

17 years ago

it's my default now..
will this theme look like the theme from this page in the future..: ?
http://www.incors.com/lookandfeel/
(reload that site for diffrent theme-color!)

anyway i like it..
thx

Report

C

dbrownlees

17 years ago

Yeah, that's the goal (in the far far distance, probably just over the horizon, never to quite be reached, but I'll try :). I've been using the WebStart demo available from that page as a reference lately.

The last two releases (0.2 & 0.3) have been primarily to fix the bugs from 0.1 (+ a few little features because I was bored). From now on I (and anyone else who's interested in helping btw) will hopefully be focusing on getting the style closer to the 'real' Alloy.

Credit at the moment must go to Simone Rota (sip, Alloy 0.1) for bringing this style to KDE, David Johnson for his sparkly clean Qinx code, and of course INCORS for creating Alloy :)

Report

sip

17 years ago

I suggest all present and future developers to have a look to some Alloy-enabled Java application, just to taste "the real thing".
A good one is Poseidon for UML (the community edition is free) at http://www.gentleware.de/
Of course another option is to play with the Alloy trial from Incors combined with your favourite Java applications.
regards,
Simone

Report

Richardve

17 years ago

I would be very thankful if you would be the first person to remove that terrible bevel from the splitter window in this theme :)

(I'd definitely use it then)

Report

C

dbrownlees

17 years ago

If you send me a screenshot (dbrownlees at paradise.net.nz) detailing what you don't like and even any suggested improvements, I'd be happy to look at changing things a bit (provided I agree with you of course ;-)

Report

Deciare

17 years ago

Thank you for continuing work on this style! The issues that prevented me from using 0.1 full time have been resolved, so I'm back to being a happy Alloy user.

The new version seems to introduce a visual glitch to read-only combo boxes, however: whenever the selection is changed, the newly selected item's text paints over the old text; that is, the old text isn't cleared.

Report

C

dbrownlees

17 years ago

A quick fix (not well tested) is to insert the following in alloy.cpp, line 1476:

painter->fillRect(rect, group.background());

Report

Deciare

17 years ago

That worked, thanks. I went with group.button() instead of group.background() for better consistency with the old look.

Report

sip

17 years ago

...just to greet Daniel (dbrownlees). Keep up the good work and make a great kde style. Cheers also to all the fine people at Incors. Bye!

Report

tbr

17 years ago

Which font is this?

Report

C

dbrownlees

17 years ago

Nimbus Sans

Report

Fingel

17 years ago

Anyone have any suggestions for a nice window decoration to go with this style? How about wallpapers or Icons? Just want to hear some people's thoughts : )

Report

abuse

17 years ago

Kniffy!

Report

bdufour

17 years ago

Korn's look when docked is strange when using this style. You can find a screenshot at http://www.sable.mcgill.ca/~bdufou1/gentoo/korn_alloy.png

Any idea on how to fix this?

Report

C

dbrownlees

17 years ago

First of all I'd look at the korn source to find out exactly what that _is_ that isn't getting drawn correctly. At a guess, I'd say it is an AlloyRect drawn over a slightly too large background, but what's causing that I have no idea :). I'll add it to the TODO.

Report

Brandybuck

17 years ago

This theme is starting to come into its own! It's looking better and better.

Report

mast3r

17 years ago

I have program based only on QT - alloy don't work. Programs KDE is OK.

In qtconfig Alloy-0.2 is visible and active. (There was not in 0.1)

Report

C

dbrownlees

17 years ago

The QT program has to use at least QT3 and be willing to load style plugins. It could be that the programs are QT2 or ignore custom styles. If qtconfig can find the plugin the it's probably installed correctly.

Report

Exdaix

17 years ago

Alloy 0.2 fixed my problem where YaST (I use SuSE) and some other root privelaged programs would not have the alloy style. Now it works perfectly. Excellent!

Report

Fingel

17 years ago

What is the default path for a KDE installation? I have many directorys with kde files in them, which one should I use for prefix in the configure script?

Report

Doc

17 years ago

It depends on your distro.
RedHat splits everything between /usr and the root dir (/). It's difficult and unconfortable to compile kde components for ReHat.
If i don't remeber bad, Mandrake installs Kde in /usr.
Debian based should be /usr/kde3.

Personally i never install kde from distro, i just install the X stuff and development stuff.
I install the whole self compiled kde in the /usr/kde

Report

C

dbrownlees

17 years ago

It depends on your distribution - however I find a good clean way to install kde stuff is to /usr/local and add 'prefixes=/usr/local' under [Directories] in my system.kdeglobals (under /etc/kde3/ in Debian. No idea about other distros).

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