User Details
- User Since
- Jan 23 2020, 5:21 PM (221 w, 6 d)
- Availability
- Available
Sep 4 2020
Jul 7 2020
Jul 4 2020
Another reason I chose solution A is because it's quite natural for me to think that the activities were designed to have their own desktops, plasmoids included. But I didn't know about the tough experience that Plasma 4 had.
Jul 3 2020
As the WallpapersModel works with image/video paths and you mentioned the lack of widgets layers, I assumed that LiveDesktopPreviews would reload these resources in memory, which would be unwanted, especially when it comes to videos; don't you think so?
Jun 1 2020
So while I'm not absolutely sure on this point, maybe the biggest benefit of migrating from script to effect (or maybe a plasmoid?) would be to avoid the limit of type of window allowed for scripts. Could this provide some integration with plasma panels and their plasmoids (like launchers)?
On second thought, although I've only thought of one disadvantage, I think it outweighs all the advantages of switching from ThumbnailItem to EffectWindow. Mixing C++ and QML elements in the same UI would make everything a nice (even impractical) mess.
The question is define the best way to implement this. KWin script? KWin effect? Plasmoid?
Right. And migrating the effects from C++ to QML can bring good results. Plasma itself shows that QML is great for building UI.
May 30 2020
May 20 2020
Zero based position parameters.
May 18 2020
May 15 2020
May 12 2020
May 10 2020
May 8 2020
toplevel.h changes removed.
Component version bumped.
Cool!
May 6 2020
Q_UNUSED semicolon removed.
I just thought of a separate list to avoid impact in possible existing scripts that currently do not filter desktop windows and may need to.
Sorry for the silly question, but should I update the version of all components or just the ClientModelByScreenAndActivity one?
activities property moved from Toplevel to AbstractClient class.
May 5 2020
Apr 30 2020
Indeed. The ideal solution would be to work with a generic ClientModel and be able to set the restrictions on the qml side, avoiding the declaration of a model for each situation.
Apr 29 2020
Apr 24 2020
Thanks for fixing this!
Apr 15 2020
Apr 14 2020
For the record, only now I went to read https://community.kde.org/Get_Involved/development. Now after solving some issues in my project, I must use Phabricator properly and maybe I can contribute with some patches to KWin.
Sorry for that mistake. For now I am solving some internal problems of my project (qml side of things) and I haven't even compiled kwin yet. After that I plan to submit some patches.
Mar 31 2020
Unfortunately, yes. I confirmed it now using the Desktop Grid effect.
Mar 30 2020
Jan 27 2020
Jan 24 2020
It would be for the opening and closing animations of the effect, which I think should be as similar as possible to the ones from Present Windows effect. But I think I can get the stacking order through the EffectWindowList stackingOrder() method of the EffectsHandlerImpl class. Anyway, thanks for your explanation.