[prev in list] [next in list] [prev in thread] [next in thread]
List: kwin
Subject: Re: overhaul of some kcm appearance
From: Thomas =?utf-8?q?L=C3=BCbking?= <thomas.luebking () web ! de>
Date: 2009-03-18 16:30:35
Message-ID: 200903181730.36450.thomas.luebking () web ! de
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Sorry for crossposting, but this likely isn't exactly kcd anymore (or the
original thread...)
http://lists.kde.org/?l=kde-core-devel&m=123738039617960&w=2
Am Wednesday 18 March 2009 schrieb Luciano Montanaro:
> is this new in SVN? Because kwin 4.2 does not seem to depend on
http://lists.kde.org/?l=kwin&m=123721562505986&w=2
> anything like that. What is the problem, exactly? And isn't there
> anything to do for those who do not care about Plasma look/mismatch
> with KWin?
> Making this support a plugin, or only enabled when using a certain
> window decoration.
I'd vote for passing this to the deco.
Currently KWin includes
- native Qt style support (for the dialogs etc.)
- the decoration plugin
- and now plasmas svg theming support
(what seems to pull in a 27MB library just to align the look of the boxswitch
box and itself drags in all libraries (like more 20megs) to make a fully
featured webbrowser...)
Now, the prominent look of KWin is defined by the deco plugin - so why
shouldn't it define the look of such items as well (as one /can/ expect kwin
to use some deco, but not necessarily run in a plasma powered environment)
All that needed to be done is to pass a QPainter and a rect down to the deco,
provide a default implementation for the box bg (aka black/white box) and if
some deco feels like pulling in plasma - just go ahead.
Otherwise KWin gets somehow strictly tied to the plasma desktop and becomes an
unusable joke for all other cases.
And while this would certainly protect plasma against replacement trials, i
doubt this is really intended.
Regards,
Thomas
[Attachment #5 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" \
content="1" /><style type="text/css">p, li { white-space: pre-wrap; \
}</style></head><body style=" font-family:'Segoe'; font-size:10pt; font-weight:400; \
font-style:normal;">Sorry for crossposting, but this likely isn't exactly kcd anymore \
(or the original thread...)<br> \
http://lists.kde.org/?l=kde-core-devel&m=123738039617960&w=2<br> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Am \
Wednesday 18 March 2009 schrieb Luciano Montanaro:<br> > is this new in SVN? \
Because kwin 4.2 does not seem to depend on<br> \
http://lists.kde.org/?l=kwin&m=123721562505986&w=2<br> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>> anything like that. What is the problem, exactly? And \
isn't there<br> > anything to do for those who do not care about Plasma \
look/mismatch<br> > with KWin?<br>
> Making this support a plugin, or only enabled when using a certain<br>
> window decoration.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>I'd vote for passing this to the deco.<br> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>Currently KWin includes<br>
- native Qt style support (for the dialogs etc.)<br>
- the decoration plugin<br>
- and now plasmas svg theming support<br>
(what seems to pull in a 27MB library just to align the look of the boxswitch box and \
itself drags in all libraries (like more 20megs) to make a fully featured \
webbrowser...)<br> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;"><br></p>Now, the prominent look of KWin is \
defined by the deco plugin - so why shouldn't it define the look of such items as \
well (as one /can/ expect kwin to use some deco, but not necessarily run in a plasma \
powered environment)<br> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;"><br></p>All that needed to be done is to pass a \
QPainter and a rect down to the deco, provide a default implementation for the box bg \
(aka black/white box) and if some deco feels like pulling in plasma - just go \
ahead.<br> <p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>Otherwise KWin gets somehow strictly tied to the plasma \
desktop and becomes an unusable joke for all other cases.<br> And while this would \
certainly protect plasma against replacement trials, i doubt this is really \
intended.<br> <p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>Regards,<br> Thomas</p></body></html>
_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic