6thpink

I've selected the directory /mnt/storage/music, which is where my music is stored (into subdirectories), but when I click on the button to scan my collection, nothing seems to happen.

I can't see anything unusual in the console output either.

Thanks for any pointers. - Sep 13 2009

Yep. It is. Native engines for gtk 2.x, qt 3.x and qt 4.x are being maintained at this moment.

There was a gtk 1.x engine as well, though it's no longer maintained (there's no easy way gtk 1.x could do everything that qtcurve does nowadays anyway, and the toolkit itself is unmaintained as far as I know). I think the last release for gtk 1.x was around 0.36 or so, if my memory serves correctly. - Aug 28 2008

Yes, on 0.42 or so, I think. - Dec 29 2007

Thanks for the quick response.

In which regards gtkzilla :P I really don't care about that either. I just figured that I would enable it be default in the ebuild because lots of people like that kind of integration. I really couldn't care less about it.

About the other issue, it is kde3.

I also grepped, but I knew beforehand that I would not find anything. That file must be some kind of lock file that portage (the Gentoo build system) puts there to prevent concurrent access of many emerge processes, I guess). I am not really certain this is an issue on the qtcurve side, so, unless you are experienced with Gentoo/ebuilds I would not advice you to spend your time looking on that. I will investigate and report if I find something, and I invite any other Gentoo user around to do the same and report any finds s/he make.

Anyway, I will also fill a bump request on the gentoo's bugzilla, and see if I can get the ebuild to work without ugly workarounds like this one.

Thanks for your attention and congratulations again for qtcurve. - Sep 24 2007

Great job, as always.

Since the build system changed, the old ebuilds no loger work, so I made to new ones for gtk2 and kde3, you can download them from http://jesgue.homelinux.org/other-files/

A couple of issues:

The gtk builds fails if I use -DQTC_MODIFY_MOZILLA=true. Is the a known issue or should I post the gcc output?

The kde ebuild can only be compiled with FEATURES="-sandbox". Cause it tries to open rw a file called /usr/qt/3/etc/settings/.qt_plugins_3.3rc.lock

I think this might be caused by some kind of hardcoded path on the makefiles, but since I haven't yet looked into cmake, I don't know right now how to diagnose this. So, if any gentoo/cmake user is around it would be cool if s/he could take a look at the issue.

For the rest, the ebuilds work just fine :)

Thanks. - Sep 24 2007

I had that option enabled, disabling it did not help. Then picked one of the pre-made themes, and now gtk applications could start ok.

I tried to turn thin menu items on again, but I can't now reproduce the problem. I have loaded the same theme I had before, that I had exported to a file previously.

My guess is that maybe I enabled an option AFTER the last time I saved the custom theme to a file. So I will keep trying to reproduce it, but for now I haven't been able to do so.

If I fails again I will let you know.

Thanks for the assitance and for you wonderful widget style. - Sep 10 2007

This gets better and better.

Thanks for qtcurve once again.

I have one problem though, with the gtk part. Gtk applications segfaults with using 0.53. Kde applications are ok.

I have tested sylpheed and gimp, similar results. You have a dump here:

http://jesgue.homelinux.org/dump.txt

And below some info that you might find useful to diagnose the problem (gentoo linux):

Portage 2.1.3.9 (default-linux/amd64/2007.0/desktop, gcc-4.2.0, glibc-2.6.1-r0, 2.6.22.1-night-r2 x86_64)
=================================================================
System uname: 2.6.22.1-night-r2 x86_64 AMD Sempron(tm) Processor 3000+
Timestamp of tree: Sun, 09 Sep 2007 18:00:01 +0000
app-shells/bash: 3.2_p17-r1
dev-lang/python: 2.5.1-r2
sys-apps/baselayout: 1.12.10-r4
sys-apps/sandbox: 1.2.18.1
sys-devel/autoconf: 2.13, 2.61-r1
sys-devel/automake: 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils: 2.18.50.0.1
sys-devel/gcc-config: 1.4.0-r2
sys-devel/libtool: 1.5.24
virtual/os-headers: 2.6.22-r2
ACCEPT_KEYWORDS="amd64 x86 ~amd64 ~x86"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -march=athlon64 -pipe -msse3"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config /var/qmail/alias /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-O2 -march=athlon64 -pipe -msse3"
DISTDIR="/var/portage/distfiles"
FEATURES="distlocks fixpackages metadata-transfer sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="http://trumpetti.atm.tut.fi/gentoo/ http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/"
LANG="es_ES.utf8"
LC_ALL="es_ES.utf8"
LINGUAS="es en"
MAKEOPTS="-j2"
PKGDIR="/var/portage/packages"
PORTAGE_RSYNC_EXTRA_OPTS="--bwlimit=50"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/var/portage"
PORTDIR_OVERLAY="/var/portage/local/layman/xeffects /var/portage/local/layman/live-ebuilds /var/portage/local"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X acl acpi alsa amd64 arts berkdb bitmap-fonts cairo cdr cli cracklib crypt cups dbus dri dvd dvdr dvdread eds emboss encode esd evo fam firefox fortran gdbm gif gnome gpm gstreamer gtk hal iconv ipv6 isdnlog jpeg kde kerberos ldap mad midi mikmod mmx mp3 mpeg mudflap ncurses nls nptl nptlonly ogg opengl openmp oss pam pcre pdf perl png pppd python qt3 qt3support qt4 quicktime readline reflection sdl session spell spl sse sse2 ssl svg tcpd tiff truetype truetype-fonts type1-fonts unicode vorbis xml xorg xv zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev ps2mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="es en" USERLAND="GNU" VIDEO_CARDS="nvidia vesa nv nouveau"
Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS




Regards. - Sep 10 2007

CraigD, I forgot to mention one thing, and I don't really know to what degree this could be implemented in qtcurve or not.

I also use this in gtkrc-2.0:

style "tooltips" = "default" {
bg[NORMAL] = "#ffd000"
fg[NORMAL] = "#000000"
}
widget "gtk-tooltips*" style "tooltips"

As you can see, it is a workaround to be able to view the text in the gtk flying tooltips. The problem is mostly the same: the gtk tooltips seems to take the text color from the same color than the gtk TextBox uses. The problem is that in dark schemes, that colour is white, which is also almost invisible over the standard yellow tips.

It would be nice to unify the look of the qt and gtk tooltips, and, in the way, make the gtk tooltips viewable without having to use those tricks on my gtkrc files.

Thanks again, qtcurve is awesome :) - Apr 14 2007

It would be nice if qtcurve could inherit the cursor color for gtk applications from the kde text color.

In "normal" color schemes it is not a big deal, and you can hardly notice any difference, but on dark color schemes the cursor is not visible in the gtk applications.

I just add these in my gtkrc-2.0

GtkWidget::cursor-color = "#8DC2DF"
GtkWidget::secondary-cursor-color = "#8DC2DF"

But it would be nice if qtcurve could do this for me, and it would improve the consistency between gtk and qt applications.

Thanks so much for qtcurve :) - Apr 13 2007

Precisely one of the strong points of qtcurve is that it happens to have parallel versions for gtk and qt, which makes then look identical. How to change the gtk theme is another thing. You could install gtk-engines-qt, that will add a dialog in kcontrol where you can choose the qtcurve theme in a list.

You could also use any of the gtk tools to change the gtk engine, I suppose.

The gtk and qt engines are separated, see in the download links that each one is contained within a different tarball. - Mar 22 2007

A good place to look for rmps is this:

http://rpm.pbone.net/

There are qtcurve packages are well, if you search for them, though to get the latest you will have either to wait for someone to make the rpm or to compile it yourself from source.

I don't use mandr* so I can't be of much help, I don't know either if it installs or not a working toolchain that you could use to compile qtcurve. Maybe any mandriva usar around that is more experienced could package it for you. - Mar 19 2007

You need to install the libstdc++ libs to be able to compile anything. I dont know if the name of the package is exactly that in SuSE, though. - Jan 06 2007

Hi, I use gtk+-2.8.20-r1 with a couple of patchs, gtk+-2.8.10-xinerama.patch and gtk+-2.8.0-multilib.patch. They are applied automatically in gentoo, so, of you want the patches or something and dont use gentoo, just let me know, I can send them to you or paste them here if you want to see what's inside them or anything. For the rest, its a clean, standard gtk+ source.

The tabs seem to be ok, I mean, that they look the same than they do in qt. The active one is a bit bigger in height and the menus are also ok.

Regards. - Aug 04 2006

Fast as always, the gimp small issue is solved, and the engine is working nicely under gtk and qt now.

Thank you and congratulations for this nice thing. - Aug 03 2006

Well, I dont think that the gimp version has anything to do with the problem, as I say, I suspect that is something related to the embeded widgets that goes into the main windows, holding the tools and such (dunno what those are in gtk+).

Gtk+ is 2.8.20-r1.

As Koral, y am running kde3-0.40 and gtk2-0.39, and it works great. I did not notice any other problem in any gtk application, though it is true that I do not use too much gtk stuff). But it is also true that any other style (including .39) works perfectly. And with .40 it just segfaults.

I will try to dig something useful in a gdb backtrace later, in a few hours (right now I am not on my box).

Thanks for all the attention and for this really wonderfull style :) - Aug 01 2006

Ooops, just noticed it.

In the previous post, where it says "violación de segmento", that means "Segmentation fault". - Jul 31 2006

I love qtcurve since I started using it, around 0.24 or so, dont remember so well...

It is a fantastic style that makes the life of people that dont suffer from the unique toolkit syndrome a bit easier.

I think I have found a small bug in .40, i cant reproduce it in .39 at all, and I think the latest gtk2 changes could be the responsible for this, but since my knowledge about gtk2 is near to null, I will just put here what I get when I run the gimp with qtcurve-0.40 (any other style or a previous version of qtcurve will result in a successfull execution of the gimp).


[code]
$ gimp
This is a development version of GIMP. Debug messages may appear here.

-:1: error: unexpected character `,', expected character `}'
-:1: error: unexpected character `,', expected character `}'

(gimp:21840): GLib-GObject-WARNING **: invalid cast from `GimpDockable' to `GtkNotebook'
gimp: fatal error: Violación de segmento
gimp (pid:21840): [E]xit, [H]alt, show [S]tack trace or [P]roceed: P

(script-fu:21841): LibGimpBase-WARNING **: script-fu: wire_read(): error

[/code]

Then it just exits, of course.

Gimp version is 2.3.10, I also tried 2.3.9, I dont think any other version will be anything different, since the error is related to the dockable stuff that is present in all versions of the gimp (in fact, gimps appears in the screen for some momments, but the dockable stuff in the main window is the only thing that is not drawn, i can even see the tip of the day window perfectly). - Jul 31 2006

In case someone is interested, I opened a bug at bugs.gentoo.org
and attached a Gentoo ebuild for this nice plugin:

http://bugs.gentoo.org/show_bug.cgi?id=184185

Regards.

-- Jesús Guerrero
- Jul 04 2007

I like simple wallpapers like these. But the tarball seems messed, only alpha masks seems to be contained within it, with the text line.

background_alfa.svg
background_alfa_GNULinux_onbutton.svg
background_alfa_GNULinux_onbutton2_bordered.svg - Apr 13 2007

I like them.

It is hard to find something that does not seem like a circus in my eyes. I'm always thankful to see something nice that is not that heavy on the eye.

Good work ;) - Jan 02 2007

Some of them seem to be from the RAD E8 iconsets, concretelly from Graphitte, I think. Some others remind me to the Nuove XT folder icons.

:P - Dec 25 2006

Ops, yes. Sorry :) - Dec 24 2006

Thanks, just a question.

Is there any sensible difference with the classic jimmac cursor theme?

Jesús. - Dec 24 2006

Tried also this:

./configure --prefix=/usr/ --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --with-x --enable-mitshm --without-xinerama --with-qt-dir=/usr/qt/3 --enable-mt --with-qt-libraries=/usr/qt/3/lib64 --disable-dependency-tracking --disable-debug --without-debug --without-arts --enable-libsuffix=64 --with-extra-includes=/usr/kde/3.5/include --with-extra-libs=/usr/kde/3.5/lib64 --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu

That is what my gentoo ebuild uses to compile kde-misc/ksmoothdock-3.6.1, which compiles and runs fine.

But 4.0 refuses to work, the same gdb backtrace. - Aug 25 2006

I used
./configure --prefix=/usr/kde/3.5/ --without-arts
make
su
make install

Then, it crashed. GDB reports:

[code]
This GDB was configured as "x86_64-pc-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /usr/kde/3.5/bin/ksmoothdock
[Thread debugging using libthread_db enabled]
[New Thread 47928304030336 (LWP 22228)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47928304030336 (LWP 22228)]
0x000000000040dc17 in KSmoothDock::updateLayout ()
(gdb) bt
#0 0x000000000040dc17 in KSmoothDock::updateLayout ()
#1 0x0000000000412dd4 in KSmoothDock::KSmoothDock ()
#2 0x000000000040daa6 in main ()
(gdb) c
Continuing.
KCrash: Application 'ksmoothdock' crashing...
KCrash cannot reach kdeinit, launching directly.

Program exited with code 0375.
[/code]

Tried also just ./configure --without-arts --prefix=/usr/ and with no prefix at all. - Aug 25 2006

I tried 3.6.1 today, removed all the old crap from ~/.ksmoothdock and ./kde/share/apps/ksmoothdock. But the creature does not appears on the screen. It compiles fine and runs fine, but I cant see anything, nor even the config dialog that should pop up (I removed all the config files).

The console as usuall says only:

└─[17]-> $ ksmoothdock
libpng error: Not a PNG file
libpng error: Not a PNG file
wallpaper loaded

But nothing more. I compiled it against 3.5 and using --without-arts.Hasn't anyone experienced a similar thing? Since there are no aparent errors I dont have any clue where to start looking. It just seems to work ok, but nothing appears. - Jan 14 2006

Compiled again manually and no difference. Thou I had to link /usr/kde/3.5/bin/ksmoothdock to /usr/bin/ksmoothdock, because otherwise I get:

┌─(jue ene 12, 21:11:39)-(i92guboj@localhost)-(~/.fvwm)-·
└─[16]-> $ ksmoothdock
-l: /usr/bin/ksmoothdock: No existe el fichero o el directorio

Maybe it is looking for something into a wrong place? - Jan 12 2006

Thanks for this new release.

BTW: Ugly fast ebuild for gentoo (the previous did not work for me, so I made this ugly hack):

=================
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/kde-misc/ksmoothdock/ksmoothdock-3.5.1.ebuild,v 1.7 2005/12/08 00:30:16 cryos Exp $

inherit kde eutils

DESCRIPTION="KSmoothDock is a dock program for KDE with smooth parabolic zooming."
HOMEPAGE="http://ksmoothdock.sourceforge.net"
SRC_URI="mirror://sourceforge/ksmoothdock/${P}.tar.gz"

SLOT="0"
LICENSE="GPL-2"
KEYWORDS="amd64 ppc sparc x86"
IUSE=""

S=${WORKDIR}/${PN}

need-kde 3.2

src_unpack() {
kde_src_unpack
}
=====================
Note that this has not been tested with arts and might completely fail to compile in your system.

I compiled it fine and seems to run fine, but I have a problem, nothing appears on the screen, in the console the only out is this:

┌─(jue ene 12, 21:04:49)-(i92guboj@localhost)-(~/.fvwm)-·
└─[11]-> $ ksmoothdock
libpng error: Not a PNG file
wallpaper loaded
wallpaper loaded

Any idea? Im using 3x2 desktops layout, if that matters. No compositte nor any other fancy stuff. - Jan 12 2006

Maybe this helps another Gentoo user or anyone getting the same error. I did: make clean make -f Makefile.cvs ./configure --prefix=/usr/kde/3.5 --without-arts make su -c 'make install' Now it compiles fine. :) - Oct 13 2005

Gentoo, kde-3.5_beta1 and qt-3.3.4-r8.

First I tried ./configure --without-arts --prefix=/usr/kde/3.5/ && make && su -c 'make install'. I got:

configure.in:43: version mismatch. This is Automake 1.9.6,
configure.in:43: but the definition used by this AM_INIT_AUTOMAKE
configure.in:43: comes from Automake 1.9.1. You should recreate
configure.in:43: aclocal.m4 with aclocal and run automake again.
make[2]: *** [Makefile.in] Error 1
make[2]: Leaving directory `/home/i92guboj/opt/kde/ksmoothdock/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/i92guboj/opt/kde/ksmoothdock'
make: *** [all] Error 2

Well, I ran "aclocal && automake" and now it start compiling ok. But at some point I get:

if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/kde/3.5/include -I/usr/qt/3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -MT confmenudialog.o -MD -MP -MF ".deps/confmenudialog.Tpo" -c -o confmenudialog.o confmenudialog.cpp; \
then mv -f ".deps/confmenudialog.Tpo" ".deps/confmenudialog.Po"; else rm -f ".deps/confmenudialog.Tpo"; exit 1; fi
confmenudialog.cpp: In member function `virtual void ConfMenuDialog::btRemove_clicked()':
confmenudialog.cpp:223: warning: comparison between signed and unsigned integer expressions
confmenudialog.cpp: In member function `virtual void ConfMenuDialog::btMoveDown_clicked()':
confmenudialog.cpp:272: warning: comparison between signed and unsigned integer expressions
confmenudialog.cpp: In member function `void ConfMenuDialog::selectedItemChanged()':
confmenudialog.cpp:345: warning: comparison between signed and unsigned integer expressions
confmenudialog.cpp: In member function `void ConfMenuDialog::saveAll()':
confmenudialog.cpp:378: warning: comparison between signed and unsigned integer expressions
confmenudialog.cpp:396:30: confmenudialog.moc: No such file or directory
make[2]: *** [confmenudialog.o] Error 1
make[2]: Leaving directory `/home/i92guboj/opt/kde/ksmoothdock/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/i92guboj/opt/kde/ksmoothdock'
make: *** [all] Error 2
- Oct 13 2005

I usually stay away from offtopics, but could not resist, maybe you should check this and "enlighten" us :P

Would you consider this as porno too?

http://www.unaaldia.net/wp-content/miguelangel001.jpg

Cause this guy has no "g" in front of that part that you consider to be soooo bad. So, if you find the previous image so nasty, this one should be a lot worse.

Maybe i am too inocent -i dont think so lol-, but I cant see the sexual intention in any of the pictures. Anyway, you will have to accept, sooner or later, that human beings are sexuated live beings, unlike amoebas.

Regards. - Aug 22 2006

Gosh... Dont ever install those things without even knowing in which arch, with wich libs, and for what version this was built for!!

[quote]
1. Shadows are calculated by CPU, but this will not slow down any system with a cpu clock higher than 1000 MHz.
[/quote]

Of course, this is scientifically measured, and everyone knows that a duron running at 950mhz will drastically slow down the performance. Seriously... Shadows in cpu, and next thing will be real transparency, won't it? Mmmm, and no cpu time taken at all. But only if your cpu is above 1ghz. Ok... [/sarcasm]

[quote]
2. This shadows don't make your X server crash. So this is a more stable replacement for xcompmgr and kompmgr
[/quote]

Ok, so, you are telling us that this will work under all possible conditions when you cant even preditc which qt version do I have installed? or which kdelibs? or if I might have any of the tango, pertty of kdehiddenvisibility patchs applied? Damn! Dont ever install this thing. I dont like absolute statements wich are made out of nothing, like "This shadow dont make your X server crash".

If someone want to try, just use the source, or prepare for disaster. :P

[quote]
3. Kwinshadow is a temporary solution. It will be useless when Xcompmgr and xorg will both be more stable. But how long will it take to wait?...
[/quote]

Ok, and you suggest to substitute compositte that is the way to go with a cpu based thing. Whats the next thing? go with nv+mesa instead of nvidia for 3d rendering? :P

Damn! This could be misleading people to the catastrophe. Dont ever use this unless you know what you are doing or prepare to reinstall kdelibs and kdebase.

And, last, but not least... Is this an unmodified patched version with the original kwin shadows patch? If yes, then ok, if not, you should release the mods that you made to the code and provide a link to the sources, otherwise, you are violating the gpl license of the original project.

I rereaded teh thing, and still dont know where this binaries come from. Please, explain better from where did you take them.

Jesús. - Aug 14 2006

I submited an updated ebuild to bugzilla, in hope that the gentoo team will update the one in portage (it's 5.1 right now).

The bug is this, here you can find the ebuild:
http://bugs.gentoo.org/show_bug.cgi?id=142574

I also suggested the addition of the ~amd64 keyword (amd64 unstable), since it works nicely in my amd64 box.

I have only found one little annoyance, nothing too severe though. In gxine, you can use this wrapper and it works great, the only problem is that the gtk dialog is also displayed. Under it (if i move the window to any other location) there is the qt open/save dialog. The gtk one is unresponsive, you can't click on it or interact with it in any way. Only the qt one is "alive". When the qt dialog is over, the gtk one goes away as well.

As I said, nothing too important. I dont use gxine so often either.

Nice work. :) - Aug 03 2006

It is a feature that I also miss, but firefox is not an option for me. It has some nice ideas, but I never liked it globally.

To have this into kde should not be so difficult. It is just a matter of creating a kpart and integrating it with the rest of apps. Konqueror accepts kpart, you can even embed konsole on it, so this should not be much different. I am not a kde developer, so, it would be nice if someone with the knowledge could deny or confirm this. - Feb 20 2006

Dunno if someone suggested this before but, would be nice to have something like 1.4 ghz instead of the full thing, the temp is much shorter so much of its space is really empty. For me the "two numbers in a single line" solution that I posted before would solve this as well... - Jan 12 2006

Until now the only option (that I know of) was ksensors (and so lm_sensors, which I dislike a lot). That or karamba, that I dislike even more.

One suggestion. The possibility to put the thrm and the frequency into a single line would be nice for the smaller kicker layouts. Anyway, it is perfectly readable for me in such layout, but having it into a single line would let you use bigger fonts when using a tiny kicker.

Thanks for sharing this :) - Jan 11 2006

Nice to see that this iconset is being continued. Really, it is a good thing to see something that breaks the teletubie-ish fashion that crystal initiated.

I like clean interfaces, and never liked crystal at all. Not to hurt, I dont say it is a bad iconset, I say that there should be more alternatives under kde.

I personally like a lot reinhardt and the flatsvg icon sets. Yours is very promising, and if it was more complete I would be using it. Still, I watch it very closely. Continue with this. Really, it worths the trouble. - Jan 12 2006

Are you making by ebuild or by hand? If making by hand you have to

./configure --prefix=`kde-config --prefix`

instead of just

./configure

If you are doing it with the ebuild it should just work. - Jan 12 2006

The ebuild fails to fetch the file thou it seems to be correct.

Just download the tarball and put it into distfiles before doing the "ebuild polyester.whatever digest". - Jan 12 2006

Im still around here, thou its been long since I posted the last time. Since I first met yakuake I liked it and have used it intensively since then.

One of the greatest aditions for me has been the polishing of the dcop interface. Now I wait for the autoshow feature but in the while, at least I can put kicker on top of the screen (where I like it) and put a button that launchs this command: "dcop yakuake DCOPInterface slotToggleState".

Continue working, I think this is really good. - Jan 07 2006

Dude, if you continue releasing such amount of aditions per single version this is going to be the best konsole in the world in about ten days or so... :) Thanks for the release. It is midnight here btw. - Oct 14 2005

Strange thing. I noticed it this morning. To reproduce I do this: open kcontrol-desktop-panels-appearance, mark (or unmark) "Enable background image", and press "Apply". Once I press apply, does not matter if I maked or unmarked the option, yakuake unshades and appears. I have to press the binding two times to close it (only one time does nothing in this case 8) I'm using kde-3.5_beta1. Has anyone noticed a similar thing or can anyone reproduce this? I want also to make a request: is it possible to put the startup notification dialog in another place? For example the right corner instead the left? If I want to start typing commands right after launching yakuake the notification hides my prompt and I cant see what Im writing until it goes away (two or three seconds may seem a short time, but it is getting annoying :) - Oct 09 2005

It depends only on how every person works. I, for example, have become an addept of sensitive borders in my daily work, thanks to fvwm. It has been so long time ago since I imported my settings to kde. In fvwm I use a 4x1 desktop layout, and have the left and right borders configured to scroll to the previous or next desktop if I go thru them. Aditionally, I have (embedded into a fvwmbuttons instance) an xterm, that unshades when I reach the top left corner, and a wmmixer, wmpop3 and some other things embedded into another fvwmbuttons instance that scrolls down when I reach the top right corner. I have also a fvwmicons embedded (again) into another fvwmbuttons that shows when I reach the bottom. More: I use sloppy focus, so, when I move the mouse into any window, that window takes the focus, but does not raise unless I click on it, so I can monitor things in one window, while I write commands in another windows, even if xterm is behind. I importer all these settings into kde and im very happy with them, the only thing that never managed to get is the auto dropdown terminal, so, i can only say that I would love to see that feature into yakuake, but, even if that is not implemented, I will continue using yakuake, because it has all the capabilities that I need, and I dont want to have xterms all around my desktop. - Oct 09 2005

No point in doing that. Yakuake is available thru its own binding, and when it is unshaded it stays always on top, so... It would be like to put the screensaver in the alt+tab list. - Oct 06 2005

This is getting really consistent. The only bug that remains still is the strange flickering opening a new tab when transparencie is on. But I never use transparencies anyway :) Thanks so much, this is close to perfect. For those wanting an ebuild I updated this to match the new directory naming (and many other fixes): http://forums.gentoo.org/viewtopic-t-269143-start-75.html - Oct 05 2005

I dont think there are already skins for yakuake, since it is a very young application and the autor is very busy fixing books and adding features (thanks to that yakuake has evolved a lot in these las couple of weeks). Still, it is very easy to modify the existing theme to create another one that fits your needs. The theme is installed into `kde-config --prefix`/share/apps/yakuake, it is a bunch of very little png files and a skin.def file, that is plain text and pretty self explanatory. - Oct 05 2005

Simple but usefull idea. I will try it, not its downloading. By the way, can you specify optional configure parameters? If not, that would be a great adition ;) - Oct 14 2005

kdm restarts the X server, the purpose of this tool is to restart kde without having to restart X. - Oct 08 2005

I know, but it is too buggy, and it is unmaintained at all since so many time ago. - Oct 05 2005

In which way is this flatter than plastik??? It is certainly flatter than keramik, but not flatter than plastik. Still, too bubble-ish. For me "flat"=industrial, and the closer that I managed to get with kde is a customized qtcurve or reinhardt theme. Search for those in this web to see what is a plain clean theme (and ultrafast also). - Oct 05 2005