Merge lp:~mc-return/compiz/compiz.merge-fix1082001-gridded-windows-jump-workspaces into lp:compiz/0.9.10

Proposed by MC Return
Status: Superseded
Proposed branch: lp:~mc-return/compiz/compiz.merge-fix1082001-gridded-windows-jump-workspaces
Merge into: lp:compiz/0.9.10
Diff against target: 631 lines (+194/-87)
4 files modified
plugins/expo/src/expo.cpp (+6/-0)
plugins/grid/grid.xml.in (+31/-26)
plugins/grid/src/grid.cpp (+155/-60)
plugins/grid/src/grid.h (+2/-1)
To merge this branch: bzr merge lp:~mc-return/compiz/compiz.merge-fix1082001-gridded-windows-jump-workspaces
Reviewer Review Type Date Requested Status
Sami Jaktholm (community) Needs Fixing
Compiz Maintainers Pending
Review via email: mp+157493@code.launchpad.net

This proposal supersedes a proposal from 2013-04-02.

This proposal has been superseded by a proposal from 2013-04-07.

Commit message

Grid:
Prevent center and corner gridded windows from jumping viewports.
(Thanks and credits for this go to Sami Jaktholm)

Prevent top and bottom gridded windows from jumping viewports by
making those semi-maximize horizontally.

Those are actually semi-maximized horizontally, so we will treat
them as such and let core handle the restoring, just like we
already do for semi-maximized vertically grid windows (left/right).

Now "Strg+Super+Down" will restore top and bottom gridded windows
correctly as well.

Also multiple gridding to top, bottom, left or right will not
overwrite the stored original size anymore.

Restore windows also when workspace switcher is active.
(Thanks and credits for this go to Sami Jaktholm)

Allow cycling for all gridded windows if explicitly specified by the
user in CCSM.

Forbid cycling through different sizes for corner and center-gridded
windows also per default, now fully fixing bug #878820 and following
the design specification by Ayatana Design there, making behaviour
consistent.

Grid xml:
Added cycle_sizes bool option, which allows the user to choose the
prefered behaviour (fixed versus flexible sizes on multiple presses
on the same grid keyboard shortcut).
Default of this option is off, cycling disabled as specified by design.

Added punctuation where missing and removed it where usually is none.
Fixed typos, improved description and titles.

Expo:
Tell grid when viewport change is in progress.
(Thanks and credits for this go to Sami Jaktholm)

Move:
Attention: There is no possibility to drag off horizontally resized
windows yet, the fix for this problem is proposed separately.

(fixes: LP: #878820, LP: #879218, LP: #882754 and LP: #1082001,
 partially fixes: #1116538, #1164332)

To post a comment you must log in.
Revision history for this message
MC Return (mc-return) wrote : Posted in a previous version of this proposal

Ping ?

Revision history for this message
Sam Spilsbury (smspillaz) wrote : Posted in a previous version of this proposal

Hey, I'm pretty busy at the moment. I'll get on to this ASAP.

On Thu, Apr 4, 2013 at 12:11 PM, MC Return <email address hidden> wrote:
> Ping ?
> --
> https://code.launchpad.net/~mc-return/compiz/compiz.merge-fix1082001-gridded-windows-jump-workspaces/+merge/156663
> Your team Compiz Maintainers is requested to review the proposed merge of lp:~mc-return/compiz/compiz.merge-fix1082001-gridded-windows-jump-workspaces into lp:compiz.

--
Sam Spilsbury

Revision history for this message
MC Return (mc-return) wrote : Posted in a previous version of this proposal

> Hey, I'm pretty busy at the moment. I'll get on to this ASAP.
>
Please take your time. I am honestly sorry for stressing.
I am just so excited that this MP already fixes 3 IMHO important
Grid usability bugs and so I was curious about your opinion... ;)

I will continue to work on it in the meantime, because I am
confident now that I am able to fully fix the bugs linked here...

Once all the bugs are fixed, I want to continue with optimization
of the logic and splitting out the various codeparts into separate
functions... - but this should probably be made in a separate MP
as this diff is already large enough, which complicates your review
effort (I am sorry for that)...

I can only ensure you that all changes are tested well and extensively
and manually by myself, which reduces the risk of errors or regressions
slipping through undetected ->
http://bazaar.launchpad.net/~mc-return/compiz/compiz.merge-fix1082001-gridded-windows-jump-workspaces/revision/3648
is an example for this ;)

Hope that I have all Grid bugs fixed, once you get to the review ;)

Revision history for this message
Sami Jaktholm (sjakthol) wrote : Posted in a previous version of this proposal

Some thoughts:
1) Top or bottom gridded windows can't be restored by dragging. The window does move up and down but doesn't snap off without pressing restore button/key (seems to be the default behavior for horizontally maximized windows).
2) Code duplication for GridTop || GridBottom case in initiateCommon. This could go like:
    if Top || Bottom || Left || Right
      *restore original geometry and change sizeHints*
      Resized = false

      if Top || Bottom
         maximize(HorzMask)
         HorzMaximized = true
         VertMaximized = false
      else
         maximize(VertMask)
         HorzMaximized = false
         VertMaximized = true

3) The easiest solution to fix bug 1082001 is to make expo send start/end_viewport_switch event at the start/end of viewport switch. Grid listens for those events and knows not to block the window movement while viewport switch is in progress. Currently only wall and rotate are emitting those events although expo and cube are also triggering viewport switches (so cube might need the change too).

The first point definitely needs fixing, the second one is just an opinion...

review: Needs Fixing
Revision history for this message
MC Return (mc-return) wrote : Posted in a previous version of this proposal

Hey sampo555 :)
Thanks a lot 4 your review, it is very appreciated.

> Some thoughts:
> 1) Top or bottom gridded windows can't be restored by dragging. The window
> does move up and down but doesn't snap off without pressing restore button/key
> (seems to be the default behavior for horizontally maximized windows).
>

I did not notice that problem, because on multimonitor systems it snaps off, once
your pointer crosses monitors when dragging.
I also have "Rotate Cube"->"Edge Flip DnD" enabled, which makes the top/bottom
gridded window restore as well.

But of course this should be no excuse. I'll try to find the problem and fix it.

> 2) Code duplication for GridTop || GridBottom case in initiateCommon. This
> could go like:
> if Top || Bottom || Left || Right
> *restore original geometry and change sizeHints*
> Resized = false
>
> if Top || Bottom
> maximize(HorzMask)
> HorzMaximized = true
> VertMaximized = false
> else
> maximize(VertMask)
> HorzMaximized = false
> VertMaximized = true
>

Yes. Will fix that also (was already on the TODO list).

> 3) The easiest solution to fix bug 1082001 is to make expo send
> start/end_viewport_switch event at the start/end of viewport switch. Grid
> listens for those events and knows not to block the window movement while
> viewport switch is in progress. Currently only wall and rotate are emitting
> those events although expo and cube are also triggering viewport switches (so
> cube might need the change too).
>

Very good observation. Actually awesome, sounds like the key to the solution. \o/
I still was unsure about the best way to approach the problem...
I think I'll have to conduct some experiments with that...

> The first point definitely needs fixing, the second one is just an opinion...
>

All of your points are valid and your review is very welcome.
They'll all get fixed ;).

sampo555, thanks for your involvement with Compiz.
I hope to see some new MPs from you soon...

P.S.: I'll change the status of this MP to "WIP", but additional comments are
always welcome...

Revision history for this message
MC Return (mc-return) wrote : Posted in a previous version of this proposal

@sampo55:
Did some experiments with making expo send the start/end_viewport_switch event at the start/end of viewport switch, but I was not able to get it right :(
The main new problem I got by doing that, was that Expo drag-and-dropping windows failed to work once Expo announces start_viewport_switch...
I am quite clueless @ the moment, so if you have a working solution or did experiments yourself, please propose a MP, so we can test it...

Revision history for this message
Sami Jaktholm (sjakthol) wrote : Posted in a previous version of this proposal

I don't have any code to show as I just checked what wall did but expo didn't. As DnD fails, I assume you're emitting those events right when expo starts/quits(?). If you emit the events only when expo calls moveViewport, it shouldn't affect DnD windows (emitting those events equals to situation without grid). So something like this could work:
  screen->handleCompizEvent ("expo","start_viewport_switch", CompOption::Vector());
  screen->moveViewport(...)
  screen->handleCompizEvent ("expo","end_viewport_switch", CompOption::Vector());

I don't have time to test it right now, but I can try it later...

Revision history for this message
MC Return (mc-return) wrote : Posted in a previous version of this proposal

> I don't have any code to show as I just checked what wall did but expo didn't.
> As DnD fails, I assume you're emitting those events right when expo
> starts/quits(?). If you emit the events only when expo calls moveViewport, it
> shouldn't affect DnD windows (emitting those events equals to situation
> without grid). So something like this could work:
> screen->handleCompizEvent ("expo","start_viewport_switch",
> CompOption::Vector());
> screen->moveViewport(...)
> screen->handleCompizEvent ("expo","end_viewport_switch",
> CompOption::Vector());
>
> I don't have time to test it right now, but I can try it later...

Yeah - that might indeed be the problem. I'll try that and will report here...
Thanks 4 your involvement, sampo555 - and sorry for spelling your synonym
incorrectly before ;)

Revision history for this message
Sami Jaktholm (sjakthol) wrote : Posted in a previous version of this proposal

That seems to work, but there's still a problem as gridded windows (corners) can't be dragged anywhere in expo (also present in the current trunk). That's because grid ignores the fact that window is dragged in expo (for valid reasons) but still stops the window from moving.

Seems a bit tricky to get this one right :)

Revision history for this message
MC Return (mc-return) wrote : Posted in a previous version of this proposal

> That seems to work, but there's still a problem as gridded windows (corners)
> can't be dragged anywhere in expo (also present in the current trunk). That's
> because grid ignores the fact that window is dragged in expo (for valid
> reasons) but still stops the window from moving.
>
> Seems a bit tricky to get this one right :)

Hehe, tricky describes it perfectly ;)
It would really be nice if you could propose the expo/cube code, as I did just get
to the point, where gridded corner windows do not jump viewports anymore, but I am
not able to drag any window in expo mode currently, which is ofc inacceptable...

Other observations:
In trunk it is currently possible to drag and drop corner-gridded windows in expo,
just dragging itself is not animated and the window disappears in one viewport and
suddenly pops up in the viewport it is dragged to once you release the mousebutton...

But on multimonitor systems it is not possible to drag the same windows from one
screen to the other, just from viewport to viewport...

Revision history for this message
MC Return (mc-return) wrote : Posted in a previous version of this proposal

One other point:
Seems the cube does not need any changes, as just rotate cube seems to be responsible
for moving windows...
If you unfold the cube (which is a cube option) and change workspace corner-gridded
windows stay in their position, so it seems no fix is needed here...

Revision history for this message
Sami Jaktholm (sjakthol) wrote : Posted in a previous version of this proposal

It seems to be very tricky to restore the gridded window inside expo. We can't use pointer location to calculate the restored position as it's absolute to the screen, not relative to expo viewport. We also can't restore it to original location as it might jump anywhere.

So there's pretty much two solutions:
1) Restore the window in place. Problem: the restored window might detach from the pointer, if the it's smaller than the gridded window (depending on where user grabs the window). This can't be easily solved as we don't know where the pointer is relative to the window.
2) Don't restore the window. If the window is moved inside expo, just forgot that it's gridded. This is less likely to cause any issues but it's not consistent with rest of grid behavior or nice thing to do to the user (I wouldn't like it).

Personally I like the first one more as it has a chance to get it right at least some times. The second option just feels a little broken. Anyways, an implementation of the first option can be found from lp:~sjakthol/compiz/grid-expo-interaction. Please test it, and if you think it's good, you can merge it to your branch and start debugging those horizontally maximized windows.

(I'm still the same guy - just did some profile reconfiguration)

Revision history for this message
MC Return (mc-return) wrote : Posted in a previous version of this proposal

> It seems to be very tricky to restore the gridded window inside expo. We can't
> use pointer location to calculate the restored position as it's absolute to
> the screen, not relative to expo viewport. We also can't restore it to
> original location as it might jump anywhere.
>
> So there's pretty much two solutions:
> 1) Restore the window in place. Problem: the restored window might detach from
> the pointer, if the it's smaller than the gridded window (depending on where
> user grabs the window). This can't be easily solved as we don't know where the
> pointer is relative to the window.
> 2) Don't restore the window. If the window is moved inside expo, just forgot
> that it's gridded. This is less likely to cause any issues but it's not
> consistent with rest of grid behavior or nice thing to do to the user (I
> wouldn't like it).
>
> Personally I like the first one more as it has a chance to get it right at
> least some times. The second option just feels a little broken. Anyways, an
> implementation of the first option can be found from lp:~sjakthol/compiz/grid-
> expo-interaction. Please test it, and if you think it's good, you can merge it
> to your branch and start debugging those horizontally maximized windows.
>
> (I'm still the same guy - just did some profile reconfiguration)

Hi, Sami Jaktholm :)

I've tested your branch now and this looks like another big improvement to me.
Everything works exactly like you described. Top job !

I also think that the solution you found is our best bet at the moment and it
will still affect just corner- and center-gridded windows to restore to original
size when dragged inside expo.

This solution is just slightly inconsistent, compared to the behaviour of grid-
semi-maximized and maximized windows, which will keep their size when dragged to
a new viewport - but it is 100 times better than the version we have in trunk now,
which also acts inconsistent and makes gridded windows jump around and follow the
user's moves in expo...

Restoring the window to original size is always the best solution, because gridding
it back requires just one shortcut, while it can be nerving to have to manually resize
to get back to original size.
Btw, there is still a working workaround for users, who want to move a corner- or center-
gridded window from one workspace to another (rotate to cube face with window) - this
one works perfectly for gridded windows as well...

I still have to apply your other improvements here, and still have to find a solution
for snapping off horizontally maximized windows correctly and easily...

Revision history for this message
MC Return (mc-return) wrote : Posted in a previous version of this proposal

> Some thoughts:
> 1) Top or bottom gridded windows can't be restored by dragging. The window
> does move up and down but doesn't snap off without pressing restore button/key
> (seems to be the default behavior for horizontally maximized windows).

Yes. The problem is actually hidden in the move plugin. The option SnapoffMaximized ()
does not take care of & CompWindowStateMaximizedHorzMask windows.

You can easily check this wrong behaviour by horizontally maximizing a window by
right-mousebutton clicking the maximize button and you'll get the same behaviour
like for top and bottom gridded windows with this branch here...

Actually I should file another bug and fix that in another branch I guess, but I
do not know, maybe I'll simply attach another bug report here...

Revision history for this message
MC Return (mc-return) wrote : Posted in a previous version of this proposal

I have now filed bug #1165198 about "Horizontally semi-maximized windows do not snap off easily"...

@Sami Jaktholm: Can you confirm ?

Revision history for this message
Sami Jaktholm (sjakthol) wrote : Posted in a previous version of this proposal

A second branch might be a better solution. Let's keep this as a fix for grid&expo problem only. Once the other fix lands, I'm ok with this (although I'm probably not the best judge as I have very narrow understanding of how this stuff actually works).

review: Approve
Revision history for this message
MC Return (mc-return) wrote : Posted in a previous version of this proposal

> A second branch might be a better solution. Let's keep this as a fix for
> grid&expo problem only. Once the other fix lands, I'm ok with this (although
> I'm probably not the best judge as I have very narrow understanding of how
> this stuff actually works).

Okay. The fix for the move snapoff problem should be relatively easy. I already
got a working solution (just a quick hack), but I am confident I can fix this
correctly soonish...

If you are interested: the problem is hidden in static void moveHandleMotionEvent (...)

There:
if (ms->optionGetSnapoffMaximized ())
does not check:
if (w->state () & CompWindowStateMaximizedHorzMask)

and thus Compiz has no strategy to snap off a horizontally semi-maximized window...

Revision history for this message
MC Return (mc-return) wrote : Posted in a previous version of this proposal

> A second branch might be a better solution. Let's keep this as a fix for
> grid&expo problem only. Once the other fix lands, I'm ok with this (although
> I'm probably not the best judge as I have very narrow understanding of how
> this stuff actually works).

I've uploaded the fix for bug #1165198 to this branch now anyway as it is somehow
related and is very separated fromthe rest (as the fix is in the move plugin).

Re-review and re-test needed ;)

Revision history for this message
Sami Jaktholm (sjakthol) wrote :

The change to move code might cause a change in behavior in a corner case. If the window is HorzMaximized but not VertMaximized, the code will never enter the next else if clause (where it would remaximize the window) as it returns in the new else if block. However I haven't found a way to trigger this case so it shouldn't be a problem.

I still think you should split these changes up as the move changes have nothing to do with the original problem.

Other than that, it looks good and works fine.

review: Approve
Revision history for this message
MC Return (mc-return) wrote :

Hey Sami :)

Thanks for the review and testing.
I have tested the changes extensively as well and could find no regressions.

/offtopic on
But during testing I found a new bug unfortunately... it seems to have nothing to do with this MP and can be reproduced in trunk as well, but a multimonitor system is needed:

1.Semi-maximize horizontally or maximize a window on monitor 2
2.Change the viewport
3.Switch back to your window with a switcher, or via click on its icon in a dock/launcher

Result: The viewport will change correctly, but the window will move to the main monitor and maximize/semi-maximize horizontally there

Can you reproduce this also (without this branch) ?
/offtopic off

Regarding move: Sure, I can make a new MP for that - my only personal problem is that my SSD is 96,8% full and each
MP with a compiled/tested Compiz build takes another 400MB away ;) - so I am quite handicapped with available space @ the moment...

Revision history for this message
MC Return (mc-return) wrote :

I've changed the partial fixes in the commit message to numbers, but I might have to remove the linked bug reports, so launchpad won't auto-track them and change them to "Fix Committed" when committing this to trunk, but I'll better adjust the status of those manually after the merge...

Revision history for this message
Sami Jaktholm (sjakthol) wrote :

I don't have a second monitor to test that.

3653. By MC Return

Grid:
Forbid cycling through different sizes for corner and center-gridded
windows also, now fully fixing bug #878820 and following the design
specification for now

TODO: Make the behaviour configurable for the user as many prefer
cycling through different sizes

Added comment
Minor whitespace fixes
Declare CompOutput out and assign a value to it in one line

Revision history for this message
MC Return (mc-return) wrote :

> I don't have a second monitor to test that.
No problem, seems to be completely unrelated anyway... will check that one @ a later stage...

We are now bailing out if we are repeating the same action:
Probably this would have been enough:

if (gw->lastTarget == where &&
    gw->isGridResized)
    return false

but it works now also (with a little bit of redundancy in the condition check) ;)

I'll have to optimize that a bit...

3654. By MC Return

Simplified the condition check to bail out if the last target was the
same like the current one to prevent corner and centered windows from
cycling through sizes

3655. By MC Return

plugins/grid/grid.xml.in:

Added cycle_sizes bool option, which allows the user to choose the
prefered behaviour (fixed versus flexible sizes on multiple presses
 on the same grid keyboard shortcut)
Default of this option is off, cycling disabled as specified by design

Added punctuation where missing and removed it where usually is none
Fixed typos, improved description and titles

grid:

Allow cycling for corner/center gridded windows if specified by the
user

Revision history for this message
MC Return (mc-return) wrote :

Okay, behaviour is configurable now (at least for corner and center gridded windows), so we won't regress for noone...

3656. By MC Return

Allow cycling through different sizes for top/bottom and left/right
gridded windows as well, if the user specified it in CCSM explicitely
(default is off)

Revision history for this message
MC Return (mc-return) wrote :

Made the behaviour now fully configurable for all gridded windows.

Revision history for this message
Sami Jaktholm (sjakthol) wrote :

This has way too much going on. Please split these changes up (one fix per MP).

review: Needs Fixing
Revision history for this message
MC Return (mc-return) wrote :

> This has way too much going on. Please split these changes up (one fix per
> MP).

I will explain first what happened after r3652, which is the last revision
you approved...
Btw, there are subcommits, which all have their own diff - making it easier
to follow development:

In
http://bazaar.launchpad.net/~mc-return/compiz/compiz.merge-fix1082001-gridded-windows-jump-workspaces/revision/3653
I forbid cycling through different sizes for corner and center-gridded
windows also, now fully fixing bug #878820 and following the design
specification for now.

In
http://bazaar.launchpad.net/~mc-return/compiz/compiz.merge-fix1082001-gridded-windows-jump-workspaces/revision/3654
I simplified the condition check to bail out if the last target was the
same like the current one to prevent corner and centered windows from
cycling through sizes, so that it looked like this:

if (gw->lastTarget == where &&
    gw->isGridResized)
    return false;

That means we bail out if the last target is the same as current one and
the window is already grid-resized, so we won't resize a corner/center
gridded window again.

In
http://bazaar.launchpad.net/~mc-return/compiz/compiz.merge-fix1082001-gridded-windows-jump-workspaces/revision/3655
I added a cycle_sizes bool option, which allows the user to choose the
prefered behaviour (fixed versus flexible sizes on multiple presses
 on the same grid keyboard shortcut).
Default of this option is off, cycling disabled as specified by design.
This is the relevant part in the xml, the rest are just minor punctuation/
wording fixes:
<option name="cycle_sizes" type="bool">
    <_short>Cycle Through Multiple Sizes</_short>
    <_long>Cycle through multiple different sizes by using the same keyboard shortcut multiple times in a row.</_long>
    <default>false</default>
</option>

The only code change in this revision is this:
/* We do not want to allow cycling through sizes,
 * unless the user explicitely specified that in CCSM */
if (gw->lastTarget == where &&
    gw->isGridResized &&
    !optionGetCycleSizes ())
    return false;

That means we allow to cycle center and corner gridded
windows now, if the user specifies explicitly in CCSM.

In the final revision
http://bazaar.launchpad.net/~mc-return/compiz/compiz.merge-fix1082001-gridded-windows-jump-workspaces/revision/3656
I had to implement the same choice for the rest of the
grid windows, namely left/right/top/bottom, which will
act like normal grid windows, if the user selects the
"want to cycle through sizes" option in CCSM

Voila, everything works perfectly :)

3657. By MC Return

Reverted r3652 as this change to the move plugin is not tightly related
to this branch and thus will be proposed seperately to reduce diff size
here

Revision history for this message
MC Return (mc-return) wrote :
3658. By MC Return

Grid:
We want to use the same functionality like the unmaximize_or_minimize_window
shortcut normally provides, so if our window has not been touched by grid, we
will do the same with that window that core would normally do
(see src/actions.cpp, unmaximizeOrMinimizeWin and
 launchpad bug LP: #1116538 for details)

Note: If we use the same shortcut for unmaximize_or_minimize_window_key (core)
and put_restore_key (grid) core will take over again, if grid gets disabled
If grid is enabled the unmaximize_or_minimize_window_key will be overridden,
because core always loads first and grid later

Also note that this commit did not change any shortcut yet, but just provides
the functionality for grid - Please use your grid restore keybinding like you
would use the unmaximize_or_minimize_window_key normally to test

3659. By MC Return

Grid xml:
Improved tooltip for the "put_restore_key" reflecting it's enhanced
functionality.

3660. By MC Return

Merged Grid from latest lp:compiz

Simplified bool GridScreen::restoreWindow (...):
If Grid has not touched the window we return false and let core do the
dirty work (Thanks go to Sam Spilsbury for suggesting this)

Improved the CCSM grid restore tooltip

3661. By MC Return

Merged latest lp:compiz

Unmerged revisions

3661. By MC Return

Merged latest lp:compiz

3660. By MC Return

Merged Grid from latest lp:compiz

Simplified bool GridScreen::restoreWindow (...):
If Grid has not touched the window we return false and let core do the
dirty work (Thanks go to Sam Spilsbury for suggesting this)

Improved the CCSM grid restore tooltip

3659. By MC Return

Grid xml:
Improved tooltip for the "put_restore_key" reflecting it's enhanced
functionality.

3658. By MC Return

Grid:
We want to use the same functionality like the unmaximize_or_minimize_window
shortcut normally provides, so if our window has not been touched by grid, we
will do the same with that window that core would normally do
(see src/actions.cpp, unmaximizeOrMinimizeWin and
 launchpad bug LP: #1116538 for details)

Note: If we use the same shortcut for unmaximize_or_minimize_window_key (core)
and put_restore_key (grid) core will take over again, if grid gets disabled
If grid is enabled the unmaximize_or_minimize_window_key will be overridden,
because core always loads first and grid later

Also note that this commit did not change any shortcut yet, but just provides
the functionality for grid - Please use your grid restore keybinding like you
would use the unmaximize_or_minimize_window_key normally to test

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'plugins/expo/src/expo.cpp'
2--- plugins/expo/src/expo.cpp 2013-03-26 22:02:39 +0000
3+++ plugins/expo/src/expo.cpp 2013-04-07 11:09:23 +0000
4@@ -247,10 +247,13 @@
5 void
6 ExpoScreen::finishWindowMovement ()
7 {
8+ CompOption::Vector o(0);
9 dndWindow->ungrabNotify ();
10
11+ screen->handleCompizEvent ("expo", "start_viewport_switch", o);
12 screen->moveViewport (screen->vp ().x () - selectedVp.x (),
13 screen->vp ().y () - selectedVp.y (), true);
14+ screen->handleCompizEvent ("expo", "end_viewport_switch", o);
15
16 /* update saved window attributes in case we moved the
17 window to a new viewport */
18@@ -486,6 +489,8 @@
19 void
20 ExpoScreen::donePaint ()
21 {
22+ CompOption::Vector o(0);
23+ screen->handleCompizEvent ("expo", "start_viewport_switch", o);
24 switch (vpUpdateMode) {
25 case VPUpdateMouseOver:
26 screen->moveViewport (screen->vp ().x () - selectedVp.x (),
27@@ -504,6 +509,7 @@
28 default:
29 break;
30 }
31+ screen->handleCompizEvent ("expo", "end_viewport_switch", o);
32
33 if ((expoCam > 0.0f && expoCam < 1.0f) || dndState != DnDNone)
34 cScreen->damageScreen ();
35
36=== modified file 'plugins/grid/grid.xml.in'
37--- plugins/grid/grid.xml.in 2013-01-16 23:12:46 +0000
38+++ plugins/grid/grid.xml.in 2013-04-07 11:09:23 +0000
39@@ -2,7 +2,7 @@
40 <compiz>
41 <plugin name="grid" useBcop="true">
42 <_short>Grid</_short>
43- <_long>Warp and resize windows to fit an imaginary grid.</_long>
44+ <_long>Warp and resize windows to fit an imaginary grid</_long>
45 <category>Window Management</category>
46 <deps>
47 <requirement>
48@@ -83,7 +83,7 @@
49 <_long>Window resize action</_long>
50 <option name="top_left_corner_action" type="int">
51 <_short>Upper Left Corner</_short>
52- <_long>Action to be performed when window is dropped on the top left corner</_long>
53+ <_long>Action to be performed when window is dropped on the top left corner.</_long>
54 <default>4</default>
55 <min>0</min>
56 <max>10</max>
57@@ -134,7 +134,7 @@
58 </option>
59 <option name="top_edge_action" type="int">
60 <_short>Top Edge</_short>
61- <_long>Action to be performed when window is dropped on the top edge</_long>
62+ <_long>Action to be performed when window is dropped on the top edge.</_long>
63 <default>10</default>
64 <min>0</min>
65 <max>10</max>
66@@ -185,7 +185,7 @@
67 </option>
68 <option name="top_right_corner_action" type="int">
69 <_short>Upper Right Corner</_short>
70- <_long>Action to be performed when window is dropped on the top right corner</_long>
71+ <_long>Action to be performed when window is dropped on the top right corner.</_long>
72 <default>6</default>
73 <min>0</min>
74 <max>10</max>
75@@ -236,7 +236,7 @@
76 </option>
77 <option name="left_edge_action" type="int">
78 <_short>Left Edge</_short>
79- <_long>Action to be performed when window is dropped on the left edge</_long>
80+ <_long>Action to be performed when window is dropped on the left edge.</_long>
81 <default>4</default>
82 <min>0</min>
83 <max>10</max>
84@@ -287,7 +287,7 @@
85 </option>
86 <option name="right_edge_action" type="int">
87 <_short>Right Edge</_short>
88- <_long>Action to be performed when window is dropped on the right edge</_long>
89+ <_long>Action to be performed when window is dropped on the right edge.</_long>
90 <default>6</default>
91 <min>0</min>
92 <max>10</max>
93@@ -338,7 +338,7 @@
94 </option>
95 <option name="bottom_left_corner_action" type="int">
96 <_short>Bottom Left Corner</_short>
97- <_long>Action to be performed when window is dropped on the bottom left corner</_long>
98+ <_long>Action to be performed when window is dropped on the bottom left corner.</_long>
99 <default>4</default>
100 <min>0</min>
101 <max>10</max>
102@@ -389,7 +389,7 @@
103 </option>
104 <option name="bottom_edge_action" type="int">
105 <_short>Bottom Edge</_short>
106- <_long>Action to be performed when window is dropped on the bottom edge</_long>
107+ <_long>Action to be performed when window is dropped on the bottom edge.</_long>
108 <default>0</default>
109 <min>0</min>
110 <max>10</max>
111@@ -440,7 +440,7 @@
112 </option>
113 <option name="bottom_right_corner_action" type="int">
114 <_short>Bottom Right Corner</_short>
115- <_long>Action to be performed when window is dropped on the bottom right corner</_long>
116+ <_long>Action to be performed when window is dropped on the bottom right corner.</_long>
117 <default>6</default>
118 <min>0</min>
119 <max>10</max>
120@@ -490,42 +490,47 @@
121 </desc>
122 </option>
123 <option name="snapoff_maximized" type="bool">
124- <_short>Snapoff maximized windows</_short>
125- <_long>Snapoff maximized windows when pulling to edge.</_long>
126+ <_short>Snapoff Maximized/Semi-maximized Windows</_short>
127+ <_long>Snapoff maximized and vertically maximized windows by dragging them up or down and horizontally maximized ones by dragging them left or right.</_long>
128 <default>false</default>
129 </option>
130 <option name="snapback_windows" type="bool">
131- <_short>Snap windows back to original size</_short>
132+ <_short>Snap Windows Back To Original Size</_short>
133 <_long>Snaps windows back to their original size if dragged away from their gridded position.</_long>
134 <default>true</default>
135 </option>
136+ <option name="cycle_sizes" type="bool">
137+ <_short>Cycle Through Multiple Sizes</_short>
138+ <_long>Cycle through multiple different sizes by using the same keyboard shortcut multiple times in a row.</_long>
139+ <default>false</default>
140+ </option>
141 </subgroup>
142 <subgroup>
143 <_short>Thresholds</_short>
144 <option name="left_edge_threshold" type="int">
145 <_short>Left Edge</_short>
146- <_long>Maximum number of pixels from the left edge a window can be dropped</_long>
147+ <_long>Maximum number of pixels from the left edge a window can be dropped.</_long>
148 <default>15</default>
149 <min>0</min>
150 <max>500</max>
151 </option>
152 <option name="right_edge_threshold" type="int">
153 <_short>Right Edge</_short>
154- <_long>Maximum number of pixels from the right edge a window can be dropped</_long>
155+ <_long>Maximum number of pixels from the right edge a window can be dropped.</_long>
156 <default>15</default>
157 <min>0</min>
158 <max>500</max>
159 </option>
160 <option name="top_edge_threshold" type="int">
161 <_short>Top Edge</_short>
162- <_long>Maximum number of pixels from the top edge a window can be dropped</_long>
163+ <_long>Maximum number of pixels from the top edge a window can be dropped.</_long>
164 <default>20</default>
165 <min>0</min>
166 <max>500</max>
167 </option>
168 <option name="bottom_edge_threshold" type="int">
169 <_short>Bottom Edge</_short>
170- <_long>Maximum number of pixels from the Bottom edge a window can be dropped</_long>
171+ <_long>Maximum number of pixels from the bottom edge a window can be dropped.</_long>
172 <default>5</default>
173 <min>0</min>
174 <max>500</max>
175@@ -535,24 +540,24 @@
176 <group>
177 <_short>Appearance</_short>
178 <option name="draw_indicator" type="bool">
179- <_short>Draw Indicator</_short>
180- <_long>Draw Window Resize Indicator</_long>
181+ <_short>Preview Indicator</_short>
182+ <_long>Draw a window resize indicator preview.</_long>
183 <default>true</default>
184 </option>
185 <option name="draw_stretched_window" type="bool">
186- <_short>Draw Stretched Window</_short>
187- <_long>Draw stretched window animation</_long>
188+ <_short>Stretched Live Window Preview</_short>
189+ <_long>Draw a stretched live window content animation.</_long>
190 <default>true</default>
191 </option>
192 <option name="animation_duration" type="int">
193- <_short>Animation Duration</_short>
194- <_long>Grid animation duration (in ms)</_long>
195+ <_short>Preview Animation Duration</_short>
196+ <_long>Preview animation duration (in ms).</_long>
197 <default>350</default>
198 <min>0</min>
199 </option>
200 <option name="outline_color" type="color">
201- <_short>Outline Color</_short>
202- <_long>Color of the resize indicator outline</_long>
203+ <_short>Preview Outline Color</_short>
204+ <_long>Color and opacity of the resize indicator preview outline.</_long>
205 <default>
206 <red>0xfbfb</red>
207 <green>0x8b8b</green>
208@@ -561,8 +566,8 @@
209 </default>
210 </option>
211 <option name="fill_color" type="color">
212- <_short>Fill Color</_short>
213- <_long>Fill color of the resize indicator</_long>
214+ <_short>Preview Fill Color</_short>
215+ <_long>Fill color and opacity of the resize indicator preview.</_long>
216 <default>
217 <red>0xfbfb</red>
218 <green>0x8b8b</green>
219
220=== modified file 'plugins/grid/src/grid.cpp'
221--- plugins/grid/src/grid.cpp 2013-03-22 11:58:33 +0000
222+++ plugins/grid/src/grid.cpp 2013-04-07 11:09:23 +0000
223@@ -63,7 +63,6 @@
224 const CompRect& slot)
225 {
226 int cw, ch;
227-
228 CompRect result = slotToRect (w, slot);
229
230 if (w->constrainNewWindowSize (result.width (), result.height (), &cw, &ch))
231@@ -169,17 +168,16 @@
232 if (props.numCellsX == 1)
233 centerCheck = true;
234
235- if (!gw->isGridResized)
236+ /* Do not overwrite the original size if we already have been gridded */
237+ if (!gw->isGridResized && !gw->isGridHorzMaximized && !gw->isGridVertMaximized)
238 /* Store size not including borders when using a keybinding */
239 gw->originalSize = slotToRect(cw, cw->serverBorderRect ());
240 }
241
242 if ((cw->state () & MAXIMIZE_STATE) &&
243 (resize || optionGetSnapoffMaximized ()))
244- {
245 /* maximized state interferes with us, clear it */
246 cw->maximize (0);
247- }
248
249 if ((where & GridMaximize) && resize)
250 {
251@@ -198,7 +196,9 @@
252 * gridded one.
253 */
254 gw->isGridResized = false;
255- gw->isGridSemiMaximized = false;
256+ gw->isGridHorzMaximized = false;
257+ gw->isGridVertMaximized = false;
258+
259 for (unsigned int i = 0; i < animations.size (); i++)
260 animations.at (i).fadingOut = true;
261 return true;
262@@ -219,20 +219,46 @@
263 (workarea.width () / props.numCellsX));
264 desiredSlot.setWidth (workarea.width () / props.numCellsX);
265
266- /* Adjust for constraints and decorations */
267- if (where & ~(GridMaximize | GridLeft | GridRight))
268- desiredRect = constrainSize (cw, desiredSlot);
269- else
270- desiredRect = slotToRect (cw, desiredSlot);
271+ if (!optionGetCycleSizes ())
272+ {
273+ /* Adjust for constraints and decorations */
274+ if (where & ~(GridMaximize |
275+ GridLeft | GridRight | GridTop | GridBottom))
276+ desiredRect = constrainSize (cw, desiredSlot);
277+ else
278+ desiredRect = slotToRect (cw, desiredSlot);
279+ }
280+ else /* (optionGetCycleSizes ()) */
281+ {
282+ /* Adjust for constraints and decorations */
283+ if (where & ~GridMaximize)
284+ desiredRect = constrainSize (cw, desiredSlot);
285+ else
286+ desiredRect = slotToRect (cw, desiredSlot);
287+ }
288
289 /* Get current rect not including decorations */
290 currentRect.setGeometry (cw->serverX (), cw->serverY (),
291 cw->serverWidth (),
292 cw->serverHeight ());
293
294+ /* We do not want to allow cycling through sizes,
295+ * unless the user explicitely specified that in CCSM
296+ */
297+ if (gw->lastTarget == where &&
298+ gw->isGridResized &&
299+ !optionGetCycleSizes ())
300+ return false;
301+
302+ /* Grid Left/Right/Top/Bottom are only valid here, if
303+ * cycling through sizes is disabled also
304+ */
305 if (desiredRect.y () == currentRect.y () &&
306 desiredRect.height () == currentRect.height () &&
307- where & ~(GridMaximize | GridLeft | GridRight) && gw->lastTarget & where)
308+ (where & ~(GridMaximize) ||
309+ (where & ~(GridLeft | GridRight | GridTop | GridBottom) &&
310+ !optionGetCycleSizes ())) &&
311+ gw->lastTarget & where)
312 {
313 int slotWidth25 = workarea.width () / 4;
314 int slotWidth33 = (workarea.width () / 3) + cw->border ().left;
315@@ -248,8 +274,8 @@
316 gw->resizeCount = 3;
317
318 /* tricky, have to allow for window constraints when
319- * computing what the 33% and 66% offsets would be
320- */
321+ * computing what the 33% and 66% offsets would be
322+ */
323 switch (gw->resizeCount)
324 {
325 case 1:
326@@ -285,7 +311,6 @@
327 }
328 else /* keys (2, 5, 8) */
329 {
330-
331 if ((currentRect.width () == desiredRect.width () &&
332 currentRect.x () == desiredRect.x ()) ||
333 (gw->resizeCount < 1) || (gw->resizeCount > 5))
334@@ -313,7 +338,8 @@
335 break;
336 case 4:
337 desiredSlot.setWidth (slotWidth33 -
338- (cw->border ().left + cw->border ().right));
339+ (cw->border ().left +
340+ cw->border ().right));
341 desiredSlot.setX (workarea.x () + slotWidth33);
342 gw->resizeCount++;
343 break;
344@@ -352,37 +378,62 @@
345
346 gw->sizeHintsFlags = 0;
347
348- /* Special case for left and right, actually vertically maximize
349- * the window */
350- if (where & GridLeft || where & GridRight)
351+ if (!optionGetCycleSizes ())
352 {
353- /* First restore the window to its original size */
354- XWindowChanges rwc;
355-
356- rwc.x = gw->originalSize.x ();
357- rwc.y = gw->originalSize.y ();
358- rwc.width = gw->originalSize.width ();
359- rwc.height = gw->originalSize.height ();
360-
361- cw->configureXWindow (CWX | CWY | CWWidth | CWHeight, &rwc);
362-
363- gw->isGridSemiMaximized = true;
364- gw->isGridResized = false;
365-
366- /* Maximize the window */
367- cw->maximize (CompWindowStateMaximizedVertMask);
368-
369- /* Be evil */
370- if (cw->sizeHints ().flags & PResizeInc)
371- {
372- gw->sizeHintsFlags |= PResizeInc;
373- gw->window->sizeHints ().flags &= ~(PResizeInc);
374+ /* Special cases for left/right and top/bottom gridded windows, where we
375+ * actually vertically respective horizontally semi-maximize the window
376+ */
377+ if (where & GridLeft || where & GridRight ||
378+ where & GridTop || where & GridBottom)
379+ {
380+ /* First restore the window to its original size */
381+ XWindowChanges rwc;
382+
383+ rwc.x = gw->originalSize.x ();
384+ rwc.y = gw->originalSize.y ();
385+ rwc.width = gw->originalSize.width ();
386+ rwc.height = gw->originalSize.height ();
387+
388+ cw->configureXWindow (CWX | CWY | CWWidth | CWHeight, &rwc);
389+
390+ if (where & GridLeft || where & GridRight)
391+ {
392+ gw->isGridVertMaximized = true;
393+ gw->isGridHorzMaximized = false;
394+ gw->isGridResized = false;
395+
396+ /* Semi-maximize the window vertically */
397+ cw->maximize (CompWindowStateMaximizedVertMask);
398+ }
399+ else /* GridTop || GridBottom */
400+ {
401+ gw->isGridHorzMaximized = true;
402+ gw->isGridVertMaximized = false;
403+ gw->isGridResized = false;
404+
405+ /* Semi-maximize the window horizontally */
406+ cw->maximize (CompWindowStateMaximizedHorzMask);
407+ }
408+
409+ /* Be evil */
410+ if (cw->sizeHints ().flags & PResizeInc)
411+ {
412+ gw->sizeHintsFlags |= PResizeInc;
413+ gw->window->sizeHints ().flags &= ~(PResizeInc);
414+ }
415+ }
416+ else /* GridCorners || GridCenter */
417+ {
418+ gw->isGridResized = true;
419+ gw->isGridHorzMaximized = false;
420+ gw->isGridVertMaximized = false;
421 }
422 }
423- else
424+ else /* if (optionGetCycleSizes ()) */
425 {
426 gw->isGridResized = true;
427- gw->isGridSemiMaximized = false;
428+ gw->isGridHorzMaximized = false;
429+ gw->isGridVertMaximized = false;
430 }
431
432 int dw = (lastBorder.left + lastBorder.right) -
433@@ -694,7 +745,6 @@
434 void
435 GridScreen::handleEvent (XEvent *event)
436 {
437- CompOutput out;
438 CompWindow *w;
439
440 screen->handleEvent (event);
441@@ -706,6 +756,7 @@
442
443 currentWorkarea = screen->getWorkareaForOutput
444 (screen->outputDeviceForPoint (pointerX, pointerY));
445+
446 if (lastWorkarea != currentWorkarea)
447 {
448 lastWorkarea = currentWorkarea;
449@@ -719,7 +770,7 @@
450 cScreen->damageRegion (desiredSlot);
451 }
452
453- out = screen->outputDevs ().at (
454+ CompOutput out = screen->outputDevs ().at (
455 screen->outputDeviceForPoint (CompPoint (pointerX, pointerY)));
456
457 /* Detect corners first */
458@@ -843,8 +894,8 @@
459
460 /* Don't allow non-pagers to change
461 * the size of the window, the user
462- * specified this size, thank-you */
463- if (isGridSemiMaximized)
464+ * specified this size */
465+ if (isGridHorzMaximized || isGridVertMaximized)
466 if (source != ClientTypePager)
467 xwcm = 0;
468 }
469@@ -868,7 +919,10 @@
470 pointerBufDx = pointerBufDy = 0;
471 grabMask = mask;
472
473- if (!isGridResized && !isGridSemiMaximized && gScreen->optionGetSnapbackWindows ())
474+ if (!isGridResized &&
475+ !isGridHorzMaximized &&
476+ !isGridVertMaximized &&
477+ gScreen->optionGetSnapbackWindows ())
478 /* Store size not including borders when grabbing with cursor */
479 originalSize = gScreen->slotToRect(window,
480 window->serverBorderRect ());
481@@ -909,8 +963,18 @@
482 {
483 window->moveNotify (dx, dy, immediate);
484
485- if (isGridResized && !isGridSemiMaximized && !GridScreen::get (screen)->mSwitchingVp)
486+ if (isGridResized &&
487+ !isGridHorzMaximized &&
488+ !isGridVertMaximized &&
489+ !GridScreen::get (screen)->mSwitchingVp)
490 {
491+ if (window->grabbed () && screen->grabExist ("expo"))
492+ {
493+ /* Window is being dragged in expo. Restore the original geometry
494+ * right away to avoid any confusion. */
495+ gScreen->restoreWindow (0, 0, gScreen->o);
496+ return;
497+ }
498 if (window->grabbed () && (grabMask & CompWindowGrabMoveMask))
499 {
500 pointerBufDx += dx;
501@@ -933,7 +997,10 @@
502 !(window->state () & MAXIMIZE_STATE))
503 {
504 lastTarget = GridUnknown;
505- if (isGridSemiMaximized && (lastState & MAXIMIZE_STATE) == CompWindowStateMaximizedVertMask)
506+ if ((isGridHorzMaximized &&
507+ (lastState & MAXIMIZE_STATE) == CompWindowStateMaximizedHorzMask) ||
508+ (isGridVertMaximized &&
509+ (lastState & MAXIMIZE_STATE) == CompWindowStateMaximizedVertMask))
510 gScreen->restoreWindow(0, 0, gScreen->o);
511 }
512 else if (!(lastState & MAXIMIZE_STATE) &&
513@@ -969,7 +1036,9 @@
514
515 GRID_WINDOW (cw);
516
517- if (!gw->isGridResized && !gw->isGridSemiMaximized)
518+ if (!gw->isGridResized &&
519+ !gw->isGridHorzMaximized &&
520+ !gw->isGridVertMaximized)
521 {
522 /* Grid hasn't touched this window or has maximized it. If it's
523 * maximized, unmaximize it and get out. */
524@@ -977,25 +1046,38 @@
525 cw->maximize(0);
526 return true;
527 }
528-
529- else if (!gw->isGridResized && gw->isGridSemiMaximized)
530+ else if (!gw->isGridResized &&
531+ gw->isGridHorzMaximized &&
532+ !gw->isGridVertMaximized)
533+ {
534+ /* Window has been horizontally maximized by grid. We only need
535+ * to restore Y and height - core handles X and width. */
536+ if (gw->sizeHintsFlags)
537+ gw->window->sizeHints ().flags |= gw->sizeHintsFlags;
538+ xwcm |= CWY | CWHeight;
539+ }
540+ else if (!gw->isGridResized &&
541+ !gw->isGridHorzMaximized &&
542+ gw->isGridVertMaximized)
543 {
544 /* Window has been vertically maximized by grid. We only need
545- * to restore the X and width - core handles Y and height. */
546+ * to restore X and width - core handles Y and height. */
547 if (gw->sizeHintsFlags)
548 gw->window->sizeHints ().flags |= gw->sizeHintsFlags;
549 xwcm |= CWX | CWWidth;
550 }
551-
552- else if (gw->isGridResized && !gw->isGridSemiMaximized)
553- /* Window is just gridded (top, bottom, center, corners). We
554- * need to handle everything. */
555+ else if (gw->isGridResized &&
556+ !gw->isGridHorzMaximized &&
557+ !gw->isGridVertMaximized)
558+ /* Window is just gridded (center, corners).
559+ * We need to handle everything. */
560 xwcm |= CWX | CWY | CWWidth | CWHeight;
561 else
562 {
563 /* This should never happen. But if it does, just bail out
564 * gracefully. */
565- assert (gw->isGridResized && gw->isGridSemiMaximized);
566+ assert (gw->isGridResized &&
567+ (gw->isGridHorzMaximized || gw->isGridVertMaximized));
568 return false;
569 }
570
571@@ -1004,6 +1086,16 @@
572 xwc.x = pointerX - (gw->originalSize.width () / 2);
573 xwc.y = pointerY + (cw->border ().top / 2);
574 }
575+ else if (cw->grabbed () && screen->grabExist ("expo"))
576+ {
577+ /* We're restoring a window inside expo by dragging. This is a bit
578+ * tricky. Pointer location is absolute to the screen, not relative
579+ * to expo viewport. So we can't use pointer location to calculate
580+ * the position of the restore window.
581+ *
582+ * The best solution is to resize it in place. */
583+ xwcm = CWWidth | CWHeight;
584+ }
585 else
586 {
587 xwc.x = gw->originalSize.x ();
588@@ -1018,7 +1110,8 @@
589 gw->currentSize = CompRect ();
590 gw->pointerBufDx = 0;
591 gw->pointerBufDy = 0;
592- gw->isGridSemiMaximized = false;
593+ gw->isGridHorzMaximized = false;
594+ gw->isGridVertMaximized = false;
595 gw->isGridResized = false;
596 if (cw->state () & MAXIMIZE_STATE)
597 cw->maximize(0);
598@@ -1035,7 +1128,8 @@
599 GRID_WINDOW (screen->findWindow
600 (CompOption::getIntOptionNamed (o, "window")));
601 gw->isGridResized = false;
602- gw->isGridSemiMaximized = false;
603+ gw->isGridHorzMaximized = false;
604+ gw->isGridVertMaximized = false;
605 gw->resizeCount = 0;
606 }
607
608@@ -1197,7 +1291,8 @@
609 gWindow (GLWindow::get(window)),
610 gScreen (GridScreen::get (screen)),
611 isGridResized (false),
612- isGridSemiMaximized (false),
613+ isGridHorzMaximized (false),
614+ isGridVertMaximized (false),
615 grabMask (0),
616 pointerBufDx (0),
617 pointerBufDy (0),
618
619=== modified file 'plugins/grid/src/grid.h'
620--- plugins/grid/src/grid.h 2013-01-21 15:17:50 +0000
621+++ plugins/grid/src/grid.h 2013-04-07 11:09:23 +0000
622@@ -182,7 +182,8 @@
623 GridScreen *gScreen;
624
625 bool isGridResized;
626- bool isGridSemiMaximized;
627+ bool isGridHorzMaximized;
628+ bool isGridVertMaximized;
629 unsigned int grabMask;
630 int pointerBufDx;
631 int pointerBufDy;

Subscribers

People subscribed via source and target branches