--===============3593925535808162687==
Content-Type: multipart/alternative; boundary=047d7b15a677dcd99c04c12b929c

--047d7b15a677dcd99c04c12b929c
Content-Type: text/plain; charset=ISO-8859-1

On Tue, May 29, 2012 at 1:51 PM, Aaron J. Seigo <aseigo@kde.org> wrote:

> On Tuesday, May 29, 2012 13:34:12 Mark wrote:
> > This is a separate project to allow Windows in Plasma QML.
>
> ok, as a separate project, i think this makes sense. i'll try to find time
> to
> discuss implementation and API later .. but maybe we should finish tooltips
> first? :)
>
> Oke :)
Why don't i get paid for this... i LIKE this!


>  > The added benefit is that tooltip control becomes much easier and that's
> > why i bring this up now. If this gets accepted then i make the tooltips
> > dependent on it.
>
> i don't think an application window and a tooltip window will have much
> useful
> overlap.
>
> i am tempted to say "use Dialog" but .. i like that Dialog remains very
> purpose specific so we don't need to try and make it do too many tricks at
> the
> same time.
>
> so maybe the answer is "re-use Dialog", or rather the code behind it. it
> does
> pretty much everything needed (blur, borders, etc.) i recommend
> implementing
> such a window class in C++ that is made available to QML inside the
> tooltips
> implementation. that way we don't have to worry too much about upfront
> design
> questions: make it work well for tooltips. then we can see what that ends
> up
> looking like and either base a design off of that or even lift that code
> out
> directly and promote it to a shared QML component.
>
>
Interesting. Though windows are different then those dialogs.
Lets keep this thread alive since the discussion for this one isn't over.
I'm only "sparking" it, you and marco probably need to agree on a good api
and how to allow window stuff.

--
> Aaron J. Seigo
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
>

--047d7b15a677dcd99c04c12b929c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Tue, May 29, 2012 at 1:51 PM, Aaron J. Seigo =
<span dir=3D"ltr">&lt;<a href=3D"mailto:aseigo@kde.org" target=3D"_blank">a=
seigo@kde.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div class=3D"im">On Tuesday, May 29, 2012 13:34:12 Mark wrote:<br>
&gt; This is a separate project to allow Windows in Plasma QML.<br>
<br>
</div>ok, as a separate project, i think this makes sense. i&#39;ll try to =
find time to<br>
discuss implementation and API later .. but maybe we should finish tooltips=
<br>
first? :)<br>
<div class=3D"im"><br></div></blockquote><div>Oke :)</div><div>Why don&#39;=
t i get paid for this... i LIKE this!</div><div>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">

<div class=3D"im">
&gt; The added benefit is that tooltip control becomes much easier and that=
&#39;s<br>
&gt; why i bring this up now. If this gets accepted then i make the tooltip=
s<br>
&gt; dependent on it.<br>
<br>
</div>i don&#39;t think an application window and a tooltip window will hav=
e much useful<br>
overlap.<br>
<br>
i am tempted to say &quot;use Dialog&quot; but .. i like that Dialog remain=
s very<br>
purpose specific so we don&#39;t need to try and make it do too many tricks=
 at the<br>
same time.<br>
<br>
so maybe the answer is &quot;re-use Dialog&quot;, or rather the code behind=
 it. it does<br>
pretty much everything needed (blur, borders, etc.) i recommend implementin=
g<br>
such a window class in C++ that is made available to QML inside the tooltip=
s<br>
implementation. that way we don&#39;t have to worry too much about upfront =
design<br>
questions: make it work well for tooltips. then we can see what that ends u=
p<br>
looking like and either base a design off of that or even lift that code ou=
t<br>
directly and promote it to a shared QML component.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br></div><div>Interesting. Though windows are different then those=
 dialogs.</div><div>Lets keep this thread alive since the discussion for th=
is one isn&#39;t over. I&#39;m only &quot;sparking&quot; it, you and marco =
probably need to agree on a good api and how to allow window stuff.</div>

<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"HOEnZb"><font =
color=3D"#888888">
--<br>
Aaron J. Seigo</font></span><br>___________________________________________=
____<br>
Plasma-devel mailing list<br>
<a href=3D"mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href=3D"https://mail.kde.org/mailman/listinfo/plasma-devel" target=3D"_b=
lank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br>
<br></blockquote></div><br>

--047d7b15a677dcd99c04c12b929c--

--===============3593925535808162687==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

--===============3593925535808162687==--