> Purely visual review:
>
> The mockup lines are not white, but either transparent white or
> transparent grey. The headings of each group are also not white.
>
> The lines in the mockup are 1px thin grey with distinct ends. The view
> has thicker lines that are brighter that taper at the ends.
>
I'll look to it.
>
> The white-space above the "Windows" header is greater than the rest.
>
Yeah, because i've commented a couple of key bindings because they are not yet implemented.
>
> Some of the key-bindings are lower case, why is that?
>
Because Compiz CompOption gives me something like that: <Super>f... I've writed a very simple function to change it in "Super + f". I think the best solution is to capitalize each word of the shortcut.
> Why are we missing some of the key bindings, like moving the focused
> window to other workspaces?
As said, some options are not yet implmented. For example, regarding "Move focused window to different workspace" I can't find it in CCSM.
> Purely visual review:
>
> The mockup lines are not white, but either transparent white or
> transparent grey. The headings of each group are also not white.
>
> The lines in the mockup are 1px thin grey with distinct ends. The view
> has thicker lines that are brighter that taper at the ends.
>
I'll look to it.
>
> The white-space above the "Windows" header is greater than the rest.
>
Yeah, because i've commented a couple of key bindings because they are not yet implemented.
>
> Some of the key-bindings are lower case, why is that?
>
Because Compiz CompOption gives me something like that: <Super>f... I've writed a very simple function to change it in "Super + f". I think the best solution is to capitalize each word of the shortcut.
> Why are we missing some of the key bindings, like moving the focused
> window to other workspaces?
As said, some options are not yet implmented. For example, regarding "Move focused window to different workspace" I can't find it in CCSM.