[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: Plasma ApplicationWindow component proposal.
From:       Mark <markg85 () gmail ! com>
Date:       2012-05-29 11:59:37
Message-ID: CAPd6JnFGK7hR6ubV_mXDVBFonTor=0RzEPqgVkXxNRjKdCWvxQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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
>
>

[Attachment #5 (text/html)]

<div class="gmail_quote">On Tue, May 29, 2012 at 1:51 PM, Aaron J. Seigo \
<span dir="ltr">&lt;<a href="mailto:aseigo@kde.org" \
target="_blank">aseigo@kde.org</a>&gt;</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 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="im"><br></div></blockquote><div>Oke :)</div><div>Why don&#39;t \
i get paid for this... i LIKE this!</div><div> </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">

<div class="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 tooltips<br> &gt; dependent on it.<br>
<br>
</div>i don&#39;t think an application window and a tooltip window will \
have much useful<br> overlap.<br>
<br>
i am tempted to say &quot;use Dialog&quot; but .. i like that Dialog \
remains 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 implementing<br> such a window class in C++ that is made \
available to QML inside the tooltips<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 \
up<br> looking like and either base a design off of that or even lift that \
code out<br> directly and promote it to a shared QML component.<br>
<span class="HOEnZb"><font \
color="#888888"><br></font></span></blockquote><div><br></div><div>Interesting. \
Though windows are different then those dialogs.</div><div>Lets keep this \
thread alive since the discussion for this 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="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span \
                class="HOEnZb"><font color="#888888">
--<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>



_______________________________________________
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