Bespin

Be-Shell/Bespin by thomas12777 1662 comments

The button color is either calculated by the hints provided by the style (and the counterpart to the background you set, i.e. "WindowText" for Window, "Text for Base" or can be set diretcly through the rules for specifc windows that are NOT hinted by the style (gtk, X11, motif, athena, wine, ...)

You can prevent the titlerbar from honoring the style hints by checking "ignore style hints" in the "tricks" tab (this settings actually belongs to the style tab, i think ;-) but then things like combined windows/titlebars or UNO won't work.

The default color for the buttos is set by KDE, but iirc they removed the UI for it - and for convenience i'll allow you to set them in the bespin deco config as well (this WE... i hope =D - Nov 27 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

No. The hack applies on runtime.
Please dump the make output into a file
make 2>&1 | tee bespin_make.log
compress and mail it to me (address on top of each source file) - Nov 26 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

-> avanti preset + "ShowOff=true" key - Nov 26 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

(i really need to delete that screenshot)

the first screenshot shows a beryl deco (it /really/ old) and bespin has no support for aqua like buttons.

If you just want to change the colors (what i'd like to discourage) you'll have to edit
~/.config/Bespi/Style.conf by hand and add
IAmMyLittleSister=true

to the deco section (she can be really insisting ;-)
then call "qdbus org.kde.kwin /KWin reconfigure" to update the deco config

THIS WILL NOT RESULT IN AQUA BUTTONS! - Nov 26 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

ah, ok... (i somewhen should update this page ;-)

sorry, but the shot is 2 1/2 years old and the deco (bespin didn't have one that time - KDE4 kwin wasn't usable at all) is from beryl.

Aqua-esque deco buttons are not intended. You can have r/g/y colored buttons - but it won't look like Aqua at all. - Nov 24 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

What screenshot shows an OS-X (aqua) look?

Anyway, bespin comes with a bunch of (atm slightly outdated) presets and a CLI tool.

You can enter the "presets" dir and
bespin try cupertino/cupertino.105a.bespin

The presets can be imported ("bespin import" or use the GUI) and used as starting point for own setups.
run
bespin [config]
or click on the configure button in
kcmshell4 style - Nov 24 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

> Is there anything preventing this from being done?

Yupp - linking kde-libs, i'd not have started the subprocess stuff otherwise anyway ;-P

The good thing is that Qt4.6 should include invoke at least kio (and hopefully kfile) anyway - so this shall become irrelevant.

Non static dialogs cannot be overridden.
(But by runtime patching the binary lib, what requires to know exact symbol offsets - i.e. not in a gcc world ;-) - Nov 24 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

For the records, it was in the static filedialog override (that apprently simply does not work this way with a couple of apps :-( - Nov 22 2009
'H' - Bespin preset

Be-Shell/Bespin by gomezhyuuga1 13 comments

Firefox is no Qt application.
If it uses Qt/Bespin at all than through a meta style (gtk-qt)
Even worse: Firefox uses it's own skinning and only wraps Gtk+ styles (i.e. if you run bespin on firefox you're on a 2nd level wrapper)

Short:
It won't work :-(
Best get a real firefox (addons/themes) skin to support it's entire skinning abilities.

Maybe i someday find the time to write a firefox skin generator ;-) - Nov 22 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

no, this took out the overlay frames entirely (i.e. most apps won't show no frames at all after this change, so revert it ;-)

luckily they seem off the hook =)

if the application "hangs", does that mean it has a high cpu load?

to "debug", try
ltrace -c [appname] > ~/bespin.ltrace
i.e. e.g.
ltrace -c vlc-player > ~/bespin.ltrace

mail me the output (bespin.ltrace, mail address in each source file)
- Nov 21 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

try commenting lines 591 & 592 in polish.cpp

// else if (!widget->inherits("KPIM::OverlayWidget"))
// VisualFrame::manage(frame);

(i hoped this was done...) and do not try to use ARGB windows on either (vlc will use XEmbed for sure and VB maybe) - Nov 21 2009
'H' - Bespin preset

Be-Shell/Bespin by gomezhyuuga1 13 comments

You need a very recent Bespin version for this (> ~826) - Nov 21 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

apparently QBoxLayout needed and extra invalidation call...
try rev844 - Nov 18 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

yes - should. does here. (esp. as the button height should equal the titlebar height)

Can you make a screenshot? - Nov 18 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

The titlebar shrinks to the minimum size (skipping frame and iirc padding) by intend.
The reason is simply tha the user (likely) wants the maximum available space for his/her app (thus the maximizing)

Also the window frame will be shrinked to (iirc) 4px

Does this cause any problems on your side? - Nov 18 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

regarding amarok:
this will become irrelevant with the new amarok release (as the old toolbar is gone, the new not re-bespinified and i'm currently working on an entirely different toolbar approach for amarok (though not as "radical" as the coolbar)

But i'm more interested in the menubar issue.
As imagebin.ce is apparently down, could you provide a scrennshot of the problem (just mail me) - Nov 14 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

fixed in rev. 820,
did sth. very stupid on the gradient cache - i'm terribly sorry (luckily you noticed it very fast)

Many Thanks - Nov 13 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

forgot:
you can run apps with a different style

kde_app --style oxygen
qt_app -style oxygen

kcmshell4 style --style oxygen
will open the style dialog with the oxygen style (but itself load bespin as current style) - Nov 13 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

that's not too great :-\
in konsole, type
gdb bespin
run

the config dialog will come up.
crash it
type (ind gdb)
bt

hit enter until you got the entire backtrace

if you cannot open konsole (for crashing) use xterm instead

sorry for the trouble - Nov 13 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

We crossed the reply maximum...

I did certainly not refer to the topscreen (mac-a-like) menubar as "weird" approach but the thing about the chainloading metastyle.

The flaws of KDE3 way were:
1. the usage of XEmbed (likely failed on gtk containers)
2. it didn't work with plain Qt QMenuBars (and there are far more plain Qt4 than there were plain Qt3 apps)

A final and /official/ solution to this would be to have an fdo (Yu Feng and myself had some ambition on this earlier this year - maybe it's time to warm them ;-) spec that's implemented by Qt directly.
The main problem on this shall be that Qt supports to place random UI elements into the menubar (what is imho a UI *sin*) - Nov 12 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

It even works for the embedded Qt styles - just not automatically (QtCurve btw has xbar support as well)

The problem isn't the "KDE upstream" their acceptance isn't even required at all (this works on a Qt only base)

It's just a weird and not very convenient approach (and has potential for some trouble if the app checks the style or the style for itself...) - Nov 11 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

I'm neither sure whether Qt has support for global config environments (so you'd have to install them on the user config - possibly overriding his stuff) nor dumping random stuff onto the user...
Also i do only semi-maintain them (i.e. they do not catch up to latter bespin config options...)

About the toolbars:
I tried that in the past and it didn't really work (and i didn't want to colorize all bars)
I just tried again and am not sure why i failed in the first run ;-) - Nov 10 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

Depending on your setup you could look at some StefanKa (Longhorn Inspirat, Lord) or Max Rudberg (Milk, * Alloy) or try the qtcurve gtk part, or -if you find a skilled gtk+ themer- i'll let the config dialog export images of the UI elements (though that's probably not far from the gtk-qt result...)

+ i've still a metastyle flying around on my disk that injects the xbar stuff into any other style - it just doesn't work automatically :-(
i.e. you'll have to pick the meta style as running one and configure it to use the resulting style, which can then no more be directly configured via the KDE config dialog :-\ - Nov 10 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

Blurring is a job for the windowmanager (i.e. kwin or compiz)
The application window (and thus the style) has no idea about what's above or below it (i.e. bespin wouldn't know what to blur)

Unfortunately KWin had to drop the blur plugin with 4.3 as it was too buggy.

IIRC Martin is working on a new blur plugin for kwin - otherwise i'll haev to start one ;-)

The preset is available (Equilibrium, ships with bespin)
I just adjusted the translucency and activated the ring overlay (can be seen in the shot =D - Nov 09 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

as firefox is not even a realy gtk+ app (thus gtk-qt stumbles) take a look at special firefox skins (there're plenty)
"vfox" is closest to safari leopard, "grayfox" appears to be a study on iTunes9 -> marble and "foxdie" is by far most configurable (and allows black tabbars. for a bright baackground enable the "glasser fix")

Or you pick one entirely different =)

As for a nice gtk+ skin: heavily depends on what you configured bespin like, but be aware that some things are just not possible with gtk+ 2.x - Nov 05 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

You need to enable ARGB support at compile time (just run ccmake (cmake built in gui) and enable it or
call "cmake -DENABLE_ARGB=ON ." in the build dir

Actually you should not the the ARGB page at all if you didn't compile it -> bug i need to fix ;-) - Nov 03 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

ensure there a file "libbespin.so" the the plugins/styles dir of your Qt base path (like /usr/lib/qt[4]/, /usr/share/qt[4]/, /opt/qt4/) and (for the integration in KDE systemsettings) "bespin.themerc" in kstyle/themes of one of the paths provided by "kde4-config --path data"

if one of them is missing there was a problem during the installation (path not found, invalid path)
-> fix that ;-) (watch the "make install" output)

in doubt you can set the style via "qtconfig" and configure it by calling "bespin" (the changes will not be exported to running apps in this case)

llod: edit the config files with e.g. kwrite
~/.config/Trolltech.conf
style=bespin
~/.kde/share/config/kdeglobals
widgetStyle=bespin
apps started after this changes would use bespin - Oct 31 2009
Intellibar formerly KWin [idea]

Various KDE Stuff by VectoR 16 comments

oo ^ =D
:-( -> =D

It's a riddle and only the wheel knows the answer ;-) - Oct 29 2009
Intellibar formerly KWin [idea]

Various KDE Stuff by VectoR 16 comments

Btw, this has been suggested before.

http://www.kde-look.org/content/show.php/Kde+for+wxga?content=96561 - Oct 28 2009
Intellibar formerly KWin [idea]

Various KDE Stuff by VectoR 16 comments

Bespin can do this (since yesterday, lefthand as scrollbars tend to be on the right)

Flaws:
- kwin has a static assumption on the shade layout (when the window is rolled into the titlebar) - it shades to the top border, whether it cotains the titlebar or not (i'll see whether i can cheat on this)
- the title label. i put it into the tooltip of the "multibutton" but in fact there's no good way to display it (whether rotated or not visible is equally bad)
However, i'm using it since a few days and except for the rare condition i open /multiple/ kwrite insances instead using kate, i could life pretty much ok without the title in sight. - Oct 28 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

Automagically? No.
First because detecting the "suitable" color (given the window content is statically colored) would mean to:
- fetch the window,
- redirect and paint it into a buffer (requires composite and conflicts with WM that make use of it - kwin/compiz)
- convert the buffer (at least the next 20 adjacent px * the width) into an bytemap (image, this is slow)
- anynalyze the image (heuristic, gradient?, what kind of? mean color...)

Second because there isn't really a global style hint (e.g. when attaching apps to presets, changing the current preset)

Third because there will still be "exceptions" (like mplayer, xine, display, etc.)

You /can/ however define a look exactly like the one in your current preset (w or w/o gradient, but differently colored) as global kwin default and define the exceptions.

Leaving aside that this will not magically follow the "stylehint de toujours" this should allow you to do what you want.

Can you drop me a mail with a sshot of the apps you'd want to align? - Oct 27 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

too late young padawan, the deco meanwhile provides custom settings ;-)

If you however want a more dynamic approach:
yes it is possible, but you'd need to either
- pass a QByteArray to qdbus (dunno how)
- add a 9 byte property to the X11 WinId (dunno how)
- write a cpp app (that's easy ;-)

so i could write you a little app that takes simple input parameters (gradients, colors) and a WId (or allows picking one) and sets the win info for that window.

The question would then be how you'd use it (i twisted my head around that as well - have the user pick the window is lame and running across the window list in a "while true" loop is the death of all performance ;-P

Feel free too call on if you have a use case and approach. - Oct 26 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

gtk-qt hasn't been updated since april :-\

FF is a special problem to gtk-qt as it uses it's own skinning mechanisms, i'd suggest to take a look at grayfox or foxdie if you're interested in a "maccish" style appeal.
Foxdie has an option for a black tabbar, grayfox is more like iTunes9 - Oct 26 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

Equilibrium with adjusted window opacity, activated air-a-like circles and glas background (everything i added with the ARGB support) - Oct 26 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

bug, fixed rev. 739 - thanks for the note - Oct 14 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

No, of course not (i don't hold a trademark on it ;-)

A reason could be that the bespin aniimation pngs are considerably HUGE, this may make your ksplashx and/or libpng stumble - i don't know :-( - Oct 08 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

You have a valid point on the volume display (i should make that "hack" optional btw...) but this is imho also a rare example.

The issue on this particular item is the direct keyboard/progress connection (usually a progressbar is not directly connected to kbd input) and the autoclosing feature.
i.e. you're right:
changing a value here and get an idea on it was pretty hard, as you had to trigger a volume button of the kbd and move the mouse at the same time - this needs two hands (and i use my right on the volume buttons as well as for the mouse either)

On the other hand the progress label is merely UI clutter under most circmstances, so I guess I want a "smarter" solution ;-)

Can you name other situations when this bothered you? - No, I'm not after a whitelist :D - Oct 06 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

you mean like alwas displaying the label?
one could easily add a flag, but please notice that i explicitly removed it to
a) calm the UI (remove useless information), because
b) the progressbar is usually a very imprecise or short term indicator (i.e. you just want to see sth. happens or the exact value isn't very reliable -esp. regarding timing- anyway)

thoughts? - Oct 05 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

the gradient is cached and only updated on palette changes, might happen to late for you?! (makes no sense... ;-)

i tried by lowering the palette swap delay (which doesn't make sense either?...)

please try rev. 700/701 (you'll unfortunately have to recompile) - Oct 04 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

not at all for the moment, sorry :-(

this is work in progress and no way even a half way finished icon theme (not even valid names and paths) - i just let TheRob push them to svn until he goes mad ;-)

There will be a script that generates a valid icon theme (subdir structure and/or tarball), but right now you can only look at them - and maybe propose fixes or own additions =D - Oct 04 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

gradient?
err (unfortunately amarok isn't visible on the screenshot, but) as i understood you, the /text/ colors were wrong.
so: is the gradient (the toolbar background) inverted compared to the window or not (so rather the background is broken and not the text) - Oct 04 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

there might be an issue if the NG bar is up on start - i'll look into it. - Oct 04 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

hmmm,
do you see a (focus colored) line under focus'd buttons? - Oct 04 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

do you use KDE from svn?

in case: this happened due to the general usage of a global stylesheet on all applications (as a result child widgets inherit the application palette instead the parents one)
This has meanwhile been reverted (it also affected knotes and others, painted focus indicators where there're not supposed to be, etc.)

You'll in this case have to update
kdelibs/kdeui/kernel/kglobalsettings.* - Oct 04 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

It just swaps QPalette::Window & QPalette::WindowText (So atm there's no way to get an entirely dark window) - Oct 04 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

should be fixed in rev. 696, please try and confirm

if anyone's interested: that's pretty funny - i wrote two dumb things a year ago, just fixed one and it turned out that two fools made a genius, but one fool is just ... a fool ;-P - Oct 04 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

copy from sf.net:
ok, finally i could reproduce it.
it's in the recent visual frame change, so you can revert that to have a quick solution.
meanwhile i'm gonna fix it - Oct 04 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

amarok (git from maybe 2h before) refuses to crash :-P

so unfortunately i'll have to see a backtrace to get any idea what this is about, sorry :-(
(esp. as my amarok isn't plain vanilla as well...)

the invalid resize request is rather unrelated (i get that with any UI style) - Oct 03 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

hmm, looks ok (i.e. not much different from mine)
so either your ksplashx version is too old (though i doubt this) or just broken (the segfault is a crash - what should not happen at all - even not with a broken description) - Oct 03 2009
Bespin

Be-Shell/Bespin by thomas12777 1662 comments

currently recompiling amarok (2 week old trunk worked)
if anyone's faster than me or it just keeps refusing to segfault on my side:

do you happen to have a backtrace? - Oct 03 2009