On Tue, May 29, 2012 at 2:24 PM, Aaron J. Seigo <ase...@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 > >
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
