Support for assigning class and their instances to tags

[dakyskye]

I am not really familiar with tagging system, but as a guy who used workspaces for months, I would like to assign some applications to certain tags by their class. This is useful if you start a couple of GUI/TUI applications at login, because if you don't assign them to tags, they will get launched in the same tag, and would be a mess! So, for example, this should do the job in the config file:

[[appRule]] # every class of Alacritty
class = 'Alacritty'
instance = ''

[appRule.assignment]
monitor = 1
tag = 3

[[appRule]] # cordless instance of Alacritty, overrides above ^
class = 'Alacritty'
instance = 'cordless'

[appRule.assignment]
monitor = 1
tag = 4

[[appRule]]
class = 'firefoxdeveloperedition'
instance = ''

[appRule.assignment]
monitor = 0
tag = 1

[dakyskye]

Titles should also be supported, because AFAIK instance and title may not match, and that makes sense.

[avahe-kellenberger]

One note, we should have it be tags and an array of tag numbers

[avahe-kellenberger]

Another note, when talking to another user, they want to be able to set a window as floating in a similar fashion.
Should have an option for class and name.

[PMunch]

With some windows assigned to tags this way it may also make sense to be able to configure the default number of masters on a per-tag basis.

[avahe-kellenberger]

@avahe-kellenberger Self ping - combine with #68, but use the method daky suggested in this issue.

[avahe-kellenberger]

@dakyskye What was your intention for instance, do you mean _NET_WM_NAME?

[dakyskye]

The instance is the first value of WM_CLASS. For example: WM_CLASS(STRING) = "cordless", "Alacritty" means it's an instance of Alacritty class called cordless. So this can be useful when you want Nimdow to assign cordless to certain tag. The other way would be using WM title, but I'd prefer a terminal instance called cordless.

[avahe-kellenberger]

@dakyskye I was thinking of doing something like this:

[[appRule]] # every class of Alacritty
class = 'Alacritty'
monitor = 2
tags = [ 3, 4 ]

[[appRule]] # cordless instance of Alacritty, overrides above ^
class = 'Alacritty'
instance = 'cordless'
monitor = 2
tags = [ 4 ]

[[appRule]]
class = 'firefoxdeveloperedition'
monitor = 1
tags = [ 1 ]

Unless there was a reason to have an appRule and appRule.assignment. Thoughts?

[dakyskye]

Yup @avahe-kellenberger that's cool. Should also support class = '*' or empty class + instance set, or title.

[avahe-kellenberger]

Started work on the app-rules branch.

Should be able to finish it this weekend, if nothing unexpected comes up.