Added dynamic version of named scratch pads

[Fresheyeball]

Description

I love named scratch pads, but they don't work with chrome apps. This is because to work with chrome apps, you need to do window selection via XMonad.Hooks.DynamicProperty, since the selection, does not exist when the window is first created.

These changes add a version of named scratch pads that can be used with an event hook. IE Event -> X All instead of ManageHook. And therefore can be used with chrome apps. I am not the only one with this problem.

Examples:

• https://bbs.archlinux.org/viewtopic.php?id=208818
• Signal (Chromium app) to workspace xmonad#31
• I swear there was more

Checklist

• I've read CONTRIBUTING.md

• I tested my changes with xmonad-testing

• I updated the CHANGES.md file

[srid]

I don't know what exactly you mean by "chrome apps" - but I can run any website as a named scratched pad using the --app parameter of chrome. For example,

scratchChromeApp name url = NS name cli windowQuery defaultFloating
  where cli = "google-chrome-stable --app=https://" <> url
        windowQuery = className =? "Google-chrome" <&&> resource =? url

scratchpads = [ scratchChromeApp "wrinkle" "myorg.wrinkle.com"
              , scratchChromeApp "irccloud" "irccloud.com"
              ]

[Fresheyeball]

@srid so by chrome app, I mean more or less what you have there, where we pass an --app flag. In my case I pass a hash instead of a url, but it's roughly the same. Now the problem with what you have there is that clicking around on the app will change the url. Also, can you tell me more about resource I have not seen that before, and it doesn't seem to correspond to anything I see using xprop. The intention of my work here was to allow chrome apps to be in a scratchpad, which I didn't see another way to accomplish.

[geekosaur]

resource is the first component of WM_CLASS. This is probably best explained by documentation of the Xrm library. Current preference in xmonad is to call it appName instead.

[srid]

Now the problem with what you have there is that clicking around on the app will change the url.

Not sure what exactly you mean by "change the url". Clicking an URL of an external domain opens that link in the current default browser (which happens to be chrome in my case). It doesn't change the state of the app.

[slotThe]

I will close this for now as, at least as far as I can tell, this comment solves this particular problem.

@Fresheyeball if you feel like that's not the case, feel free to re-open (and possibly restate the problem you're having, 2018 was quite some time ago :)

[Fresheyeball]

@slotThe no his comment does NOT address this problem. Chrome apps have unstable window properties and supporting them in scratchpads requires this change.