[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 12:29:17
Message-ID: CAPd6JnH-87XfGs1FV8MTbXVojnpMactvLW5v2RgH_LjDq-f_sQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Tue, May 29, 2012 at 2:24 PM, Aaron J. Seigo <aseigo@kde.org> wrote:
> On Tuesday, May 29, 2012 13:53:47 Mark wrote:
> > Ahh oke, i get it.
> > For the moment i can even try to use a QGraphicsProxyWidget and just send
> > WindowPreview to QML. It actually seems fairly easy to do as described
> > here:
> >
> http://qt-project.org/doc/qt-4.8/declarative-cppextensions-qwidgets-qwidgets
> > -cpp.html or
> > if it doesn't work i can always put a big red squared stub in it as
> > placeholder ^_-
>
> heh.. yes.. for getting devel going, a placeholder is fine.
>
> as marco noted, a proxy widget isn't going to be much help. what is needed
> is
> a QML element that knows of the top level window so it can set xatoms as
> needed (and later whatever we do for wayland, etc).
>
> so to me it makes sense to have this particular QML item be a C++ subclass
> of
> QDeclarativeItem that is tightly coupled to the window implementation and
> has
> a property for the window id to show.
>
> one question would be whether to support showing multiple windows in one of
> these items, or one window per item. i lean towards one window per item for
> ease of implementation and flexibility of use inside the QML.
>
Certainly 1! then a list of those elements when there are multiple.
Showing it would probably be with either a Row {} or Column {} depending on
the orientation.
>
> (and yes, with the xatom approach we'll run into repaint latency issues if
> these are highly animated ... but let's start with this and then start
> experimenting from there.)
>
> --
> 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 2:24 PM, 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 Tuesday, May 29, 2012 13:53:47 Mark wrote:<br>
> Ahh oke, i get it.<br>
> For the moment i can even try to use a QGraphicsProxyWidget and just send<br>
> WindowPreview to QML. It actually seems fairly easy to do as described<br>
> here:<br>
> <a href="http://qt-project.org/doc/qt-4.8/declarative-cppextensions-qwidgets-qwidgets" \
target="_blank">http://qt-project.org/doc/qt-4.8/declarative-cppextensions-qwidgets-qwidgets</a><br>
</div>> -cpp.html or<br>
<div class="im">> if it doesn't work i can always put a big red squared stub \
in it as<br> > placeholder ^_-<br>
<br>
</div>heh.. yes.. for getting devel going, a placeholder is fine.<br>
<br>
as marco noted, a proxy widget isn't going to be much help. what is needed is<br>
a QML element that knows of the top level window so it can set xatoms as<br>
needed (and later whatever we do for wayland, etc).<br>
<br>
so to me it makes sense to have this particular QML item be a C++ subclass of<br>
QDeclarativeItem that is tightly coupled to the window implementation and has<br>
a property for the window id to show.<br>
<br>
one question would be whether to support showing multiple windows in one of<br>
these items, or one window per item. i lean towards one window per item for<br>
ease of implementation and flexibility of use inside the \
QML.<br></blockquote><div><br></div><div>Certainly 1! then a list of those elements \
when there are multiple.</div><div>Showing it would probably be with either a Row {} \
or Column {} depending on the orientation. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <br>
(and yes, with the xatom approach we'll run into repaint latency issues if<br>
these are highly animated ... but let's start with this and then start<br>
experimenting from there.)<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>
_______________________________________________
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