Rename ShellClient to XdgShellClient
ClosedPublic

Authored by zzag on Aug 30 2019, 10:09 PM.

Details

Reviewers
None
Group Reviewers
KWin
Commits
R108:168ea98845a0: Rename ShellClient to XdgShellClient
Summary

Rename ShellClient to XdgShellClient in order to reflect that it
represents only xdg-shell clients.

Test Plan

Compiles, tests still pass.

Diff Detail

Repository
R108 KWin
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
zzag created this revision.Aug 30 2019, 10:09 PM
Restricted Application added a project: KWin. · View Herald TranscriptAug 30 2019, 10:09 PM
Restricted Application added a subscriber: kwin. · View Herald Transcript
zzag requested review of this revision.Aug 30 2019, 10:09 PM
zzag added a comment.Aug 30 2019, 10:16 PM

I'm not sure what parent revision has to be. :|

My local branch looks like this at the moment

* fbb743f59 - (37 minutes ago) Rename ShellClient to XdgShellClient - Vlad Zagorodniy (HEAD -> drop-wl-shell, github/drop-wl-shell)                                                                                    
* 864a19944 - (27 hours ago) [wayland] Drop xdg-shell v5 support - Vlad Zagorodniy                                                                                                                                     
* 3e633bc12 - (33 hours ago) [tests] Drop wl-shell test client - Vlad Zagorodniy                                                                                                                                       
* 2f2c9b1f0 - (2 days ago) [effects/slidingpopups] Don't start animation if there is no slide edge - Vlad Zagorodniy
* 336154ca5 - (2 days ago) [platforms/wayland] Drop wl-shell support - Vlad Zagorodniy
* 522673b0e - (3 days ago) [wayland] Drop wl-shell support - Vlad Zagorodniy
* cd608fd07 - (3 days ago) [autotests] Don't test wl-shell clients - Vlad Zagorodniy
* 91d6d9dd7 - (5 days ago) Port QPA away from Wayland - Vlad Zagorodniy

I don't have a strong opinion about that but I feel we could leave the ShellClient name since it's shorter and there is no ambiguity anyway when there are only xdg-shell clients. One could add a comment to the class that these instances represent xdg-shell clients.

zzag added a comment.Sep 23 2019, 3:46 PM

I don't have a strong opinion about that but I feel we could leave the ShellClient name since it's shorter and there is no ambiguity anyway when there are only xdg-shell clients. One could add a comment to the class that these instances represent xdg-shell clients.

It seems like you want to leave a room for other protocols in ShellClient class, however as far as I can tell you keeping wl-shell and xdg-shell in one class (ShellClient) was a bad idea. "Fixing" xdg-shell could easily break wl-shell and complexity of the code was a bit high.

Given that you don't have a strong opinion on this one, I'll land this patch as is.

This revision was not accepted when it landed; it landed in state Needs Review.Sep 23 2019, 3:52 PM
This revision was automatically updated to reflect the committed changes.

Belated +1.

FWIW, at some point I wanted to split this out into

-> ShellClient (Abstract superclass)

-> XdgShellTopLevel
-> XdgShellPopup

I think it'll help clean up a lot.

FWIW, at some point I wanted to split this out into

-> ShellClient (Abstract superclass)
   -> XdgShellTopLevel
   -> XdgShellPopup

Does this mean you want to go back to using the ShellClient name or was it a typo and you did mean XdgShellClient for the abstract superclass?

Does this mean you want to go back to using the ShellClient name or was it a typo and you did mean XdgShellClient for the abstract superclass?

I mean there's going to be changes to be XdgBlahBlah on all the important code anyway. I don't care what the superclass name is.