Hello again!
Heres an new Version of my Classes. Please close the other thread. He went too big.
New:
-> For Both Linux + Windows
-> ARGB under Windows / not under Linux
-> Buttons can glow under Mouse
Hello again!
Heres an new Version of my Classes. Please close the other thread. He went too big.
New:
-> For Both Linux + Windows
-> ARGB under Windows / not under Linux
-> Buttons can glow under Mouse
Next time put some screenshots in the post .
We already know what the code can do(at least me), now just want to see how it looks.
Screenshot:
Now the classes are available at qt-apps.org
Please take a look, because they now have an option which makes widgets look like
Vista Aero Widgets.
http://qt-apps.org/content/show.php?content=67309
I hate to be a spoil-sport, but I have some comments on your work. Don't you think you are entering the competence of a window manager? From what I understand you get rid of standard window decorations by creating frameless windows and draw the "skin" yourself, correct? That's exactly what a window manager is supposed to do. Using your approach one breaks one of the fundamental features of Qt - platform integration. Qt apps are meant to blend into the operating system and look exactly the same as "native" applications. If one changes the theme in the window manager (be it Aero, Aqua or KDE), Qt applications will adjust. This is not the case with your approach (although of course you've done a great job in doing what you did, it looks neat), so the use of your component is really limited. Especially on X11 platforms and when KDE4 enters the scene, your solution will become obsolete on this platform. In my opinion you are doing a step back here - you are "forcing" the programmer to think about low-level things (like borders, decorations, skins, window geometry etc.) instead of hiding those details from him. I admit your solution is pretty, but I'm not sure if it is a step in the right direction.
it's not mentured to be used for big apps...
it's something what you can use for small tools, which shouldn't look like normal apps...
i understand what you mean, but sometimes it's nice to have another decoration than the normal apps, or?
For an IDE or an EMail CLient or an internet browser i would never use this classe, because it doesn't fit, but for eg a pdf printer (windows), or chat program it's not bad, or?
The point is that it is the end-user who should decide how the application looks like and not the programmer. Looking at the screenshot you provided I see you actually try to mimic the look of real Windows decorations. The type of application doesn't really matter here.
I mean that the idea itself is ok, it's just that I think you are doing it on a wrong level. If you implemented it as a window manager decorator or even a QStyle subclass (with some style hacking of course) it would be a general use approach.
hm, ok...
but for style hacking i have to hook the window manager and than it isn't multiplatform anymore....
No no... by the style I mean QStyle and hacking involves things like setting proper pixel metrics and stuff. But really, I have nothing against your approach - I just think its usefulness might be very limited. And of course slower than drawing directly on a widget (actually to the backstore).
how can i do this?
show me code and i will try!
I don't have a ready solution for everything.
Bookmarks