[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: Re: The tooltip state. Not that good. Proposal for improvement.
From: Mark <markg85 () gmail ! com>
Date: 2012-05-29 8:28:20
Message-ID: CAPd6JnH0RgNFWnQLxj_CEu+5XBEqT+6UnENhDdn483TffkNjmQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Mon, May 28, 2012 at 12:34 AM, Aaron J. Seigo <aseigo@kde.org> wrote:
> On Sunday, May 27, 2012 21:15:30 Mark wrote:
> > You perhaps made the mental leap, for met it's still "KDE" without the
> SC.
> > It's just the way people call KDE and that sticks. the SC seems like some
> > expra part that people don't seem to remember.
>
> "SC" is part of the engineering jargon we use: it's the combined release of
> lots of separate modules. we don't use that term in public communication
> ("marketing", etc) and there's a reason for that.
>
> regardless, what i said had nothing at all to do with the SC, but rather
> about
> the technical design of the code base and where the lines of separation
> exist.
>
> for those of us working on the technology, it's really important to
> understand
> the separation between the libraries, workspaces and applications because
> that
> affects the technical decisons we allow ourselves to make.
>
> --
> Aaron J. Seigo
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
>
This tooltip stuff just got a whole lot more complicated. I asked Martin
(added to cc) for information about the window previews in QML. The reply i
got was very surprising!
------------------
Hi Mark,
window previews can only be done in KWin and not in Plasma. IMHO the
complete
tooltip functionality has to be moved to KWin for exactly that reason. In
fact
I want to do more about it, like rendering unscaled window decorations
around
the preview which have a working close button. These are things only
possible
from inside KWin.
Cheers
------------------
Yeah, he wants to move tooltips to KWin! That certainly is interesting to
say the least and that is kinda blocking what i'm doing right now with the
tooltips.
So how is this going to work if it's in KWin?
How will this be put in a library if the tooltips depend on KWin.. Surely
it's not the intention to let Dolphin depend on KWin for the tooltips?
I would like to continue this tooltip effort and finish it, but i do need
to know where this is going to. Are the window previews "somehow" going to
be posible in QML outside of KWin so that everything stays the same as it
is tight now only with QML? Or is everything going to move to KWin? In the
latte one i really need help getting it there. KWin is complex!
Feedback - lots of it - is certainly helpful now since i just don't know
where tooltips are supposed to be ending up. :)
And getting everyone informed so that we all know who is doing what seems
to be helpful in this situation as well ^_-
Cheers,
Mark
[Attachment #5 (text/html)]
<div class="gmail_quote">On Mon, May 28, 2012 at 12:34 AM, Aaron J. Seigo <span \
dir="ltr"><<a href="mailto:aseigo@kde.org" \
target="_blank">aseigo@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
<div class="im">On Sunday, May 27, 2012 21:15:30 Mark wrote:<br>
> You perhaps made the mental leap, for met it's still "KDE" without \
the SC.<br> > It's just the way people call KDE and that sticks. the SC seems \
like some<br> > expra part that people don't seem to remember.<br>
<br>
</div>"SC" is part of the engineering jargon we use: it's the combined \
release of<br> lots of separate modules. we don't use that term in public \
communication<br> ("marketing", etc) and there's a reason for that.<br>
<br>
regardless, what i said had nothing at all to do with the SC, but rather about<br>
the technical design of the code base and where the lines of separation exist.<br>
<br>
for those of us working on the technology, it's really important to \
understand<br> the separation between the libraries, workspaces and applications \
because that<br> affects the technical decisons we allow ourselves to make.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Aaron J. Seigo</font></span><br>_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br> \
<br></blockquote></div><br><div>This tooltip stuff just got a whole lot more \
complicated. I asked Martin (added to cc) for information about the window previews \
in QML. The reply i got was very surprising!</div><div><br>
</div><div>------------------</div><div><span style>Hi Mark,</span><br style><br \
style><span style>window previews can only be done in KWin and not in Plasma. IMHO \
the complete</span><br style><span style>tooltip functionality has to be moved to \
KWin for exactly that reason. In fact</span><br style>
<span style>I want to do more about it, like rendering unscaled window decorations \
around</span><br style><span style>the preview which have a working close button. \
These are things only possible</span><br style><span style>from inside \
KWin.</span><br style>
<br style><span style>Cheers</span></div><div>------------------
</div><div><br></div><div>Yeah, he wants to move tooltips to KWin! That certainly is \
interesting to say the least and that is kinda blocking what i'm doing right now \
with the tooltips.</div><div>So how is this going to work if it's in KWin?</div>
<div>How will this be put in a library if the tooltips depend on KWin.. Surely \
it's not the intention to let Dolphin depend on KWin for the \
tooltips?</div><div><br></div><div>I would like to continue this tooltip effort and \
finish it, but i do need to know where this is going to. Are the window previews \
"somehow" going to be posible in QML outside of KWin so that everything \
stays the same as it is tight now only with QML? Or is everything going to move to \
KWin? In the latte one i really need help getting it there. KWin is complex!</div>
<div><br></div><div>Feedback - lots of it - is certainly helpful now since i just \
don't know where tooltips are supposed to be ending up. :)</div><div>And getting \
everyone informed so that we all know who is doing what seems to be helpful in this \
situation as well ^_-</div>
<div><br></div><div>Cheers,</div><div>Mark</div>
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic