Re: Separate virtual desktops for different monitors

--===============3600685721809366306==
Content-Type: multipart/alternative; boundary=20cf307f318878569805108ff9e5

--20cf307f318878569805108ff9e5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 5, 2015 at 11:53 AM, Pavel Kretov <[email protected]>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> | I think there is a chance to get it part of the standard, but given
> | that most "mainstream window managers" are working on Wayland
> | currently I wouldn't expect that they will implement support for
> | it. On Wayland it is just an internal detail to the window
> | manager.
>
> Erm... How can it be so? I cannot believe Wayland is not going to
> introduce a standard of some kind for windows management? This is
> political design decision or Wayland team just didn't developed their
> specifications yet?
>

Wayland considers window management the responsibility of the Wayland
compositor, for security and simplicity reasons. There are no standard APIs
to support external panels or pagers, though some compositors and desktop
environments might develop their own.


> | You need to prepare a change to the spec. The tricky part here is
> | to keep backwards compatibility. We must expect that some
> | applications do "smart" things like stopping video playback if they
> | are not on the current desktop. (That's the main reason why KWin
> | didn't go the road i3 went: we cannot break existing
> | applications).
>
> Thank you a lot for interesting example. I had some ideas about
> possible implementation, but now things got a bit more complicated.
> I think I need to figure out more use cases like that one.
>
> =E2=80=94=E2=80=94=E2=80=94 Pavel Kretov.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: GPGTools - https://gpgtools.org
>
> iQIcBAEBCgAGBQJU+LQiAAoJEHpTboV0Z/GsTnkP/AsQC1KaKlsNICqbgUDCuESw
> /yKYbcmj2vCB8HXhLAN6yrqfMOartG5mb4MUaPKHU/zyS6S8q7nQvL3TbsWCXxMb
> CWzcZ3p/ewfTExdLED72H+RRqbhVmcUwWjKu/nwaHPIoXR48NXNjCWWrt9h9MQiH
> wSSDIOh4SqqGcF8a15g2vSp02b88FuitnRqc5WO26V2SQGHMPGttGSI3VdVj6S1+
> bbgf/g4+jxB5Eg02y/CZsdYVbb9My36uRckTe0Xz4RHoJageyuZaGa2QSeqeOdqH
> 8QVN5/ZW7BRBP6jezyAcdxFTeGaaiLpa9xyK6ZlEw4yj1Znd+ICL91fuQePNTuO5
> Ew3kTSG/n96dbC2DUVdmoBqSvSz0QlirlcX7JFNtOAproO4Zhh5WuvJDjoigrxSt
> /ll6U3Tg/ut4pyxsBWfEX1Ou7buM5yrby4Iy+ExrdJPjg0vnNXBgK1j/RvsqJDBQ
> 8P0lWXgNNl6JMG7JURYNJg7dLdZUI9pVidl8WbGdol1Qcz4r270EeDsGfzs9Waze
> hhvF5mE3Qywni1ATP01psCGYsDVIEXvs8hk3nNaSZLkqabw08Mhe5xCJG5R5DAzh
> 7pd+EG925oHdQ+xKXYYVOZK09kLNiQUDE979MmmUkw4DoYAKIwJqXGC45MLnkJyz
> LVK+UuATk07bs3G5e91w
> =3DouEQ
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> wm-spec-list mailing list
> [email protected]
> https://mail.gnome.org/mailman/listinfo/wm-spec-list
>



--=20
  Jasper

--20cf307f318878569805108ff9e5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Mar 5, 2015 at 11:53 AM, Pavel Kretov <span dir=3D"ltr">&lt;<a =
href=3D"mailto:[email protected]" target=3D"_blank">firegurafiku@gmail=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP=
 SIGNED MESSAGE-----<br>
Hash: SHA512<span class=3D""><br>
<br>
| I think there is a chance to get it part of the standard, but given<br>
| that most &quot;mainstream window managers&quot; are working on Wayland<b=
r>
| currently I wouldn&#39;t expect that they will implement support for<br>
| it. On Wayland it is just an internal detail to the window<br>
| manager.<br>
<br></span>
Erm... How can it be so? I cannot believe Wayland is not going to<br>
introduce a standard of some kind for windows management? This is<br>
political design decision or Wayland team just didn&#39;t developed their<b=
r>
specifications yet?<span class=3D""><br></span></blockquote><div><br></div>=
<div>Wayland considers window management the responsibility of the Wayland =
compositor, for security and simplicity reasons. There are no standard APIs=
 to support external panels or pagers, though some compositors and desktop =
environments might develop their own.<br></div><div>=C2=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><span class=3D"">
| You need to prepare a change to the spec. The tricky part here is<br>
| to keep backwards compatibility. We must expect that some<br>
| applications do &quot;smart&quot; things like stopping video playback if =
they<br>
| are not on the current desktop. (That&#39;s the main reason why KWin<br>
| didn&#39;t go the road i3 went: we cannot break existing<br>
| applications).<br>
<br></span>
Thank you a lot for interesting example. I had some ideas about<br>
possible implementation, but now things got a bit more complicated.<br>
I think I need to figure out more use cases like that one.<br>
<br>
=E2=80=94=E2=80=94=E2=80=94 Pavel Kretov.<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1<br>
Comment: GPGTools - <a href=3D"https://gpgtools.org" target=3D"_blank">http=
s://gpgtools.org</a><br>
<br>
iQIcBAEBCgAGBQJU+<u></u>LQiAAoJEHpTboV0Z/GsTnkP/<u></u>AsQC1KaKlsNICqbgUDCu=
ESw<br>
/<u></u>yKYbcmj2vCB8HXhLAN6yrqfMOartG5<u></u>mb4MUaPKHU/<u></u>zyS6S8q7nQvL=
3TbsWCXxMb<br>
CWzcZ3p/ewfTExdLED72H+<u></u>RRqbhVmcUwWjKu/<u></u>nwaHPIoXR48NXNjCWWrt9h9M=
QiH<br>
wSSDIOh4SqqGcF8a15g2vSp02b88Fu<u></u>itnRqc5WO26V2SQGHMPGttGSI3VdVj<u></u>6=
S1+<br>
bbgf/g4+jxB5Eg02y/<u></u>CZsdYVbb9My36uRckTe0Xz4RHoJage<u></u>yuZaGa2QSeqeO=
dqH<br>
8QVN5/<u></u>ZW7BRBP6jezyAcdxFTeGaaiLpa9xyK<u></u>6ZlEw4yj1Znd+ICL91fuQePNT=
uO5<br>
Ew3kTSG/<u></u>n96dbC2DUVdmoBqSvSz0QlirlcX7JF<u></u>NtOAproO4Zhh5WuvJDjoigr=
xSt<br>
/ll6U3Tg/<u></u>ut4pyxsBWfEX1Ou7buM5yrby4Iy+<u></u>ExrdJPjg0vnNXBgK1j/RvsqJ=
DBQ<br>
8P0lWXgNNl6JMG7JURYNJg7dLdZUI9<u></u>pVidl8WbGdol1Qcz4r270EeDsGfzs9<u></u>W=
aze<br>
hhvF5mE3Qywni1ATP01psCGYsDVIEX<u></u>vs8hk3nNaSZLkqabw08Mhe5xCJG5R5<u></u>D=
Azh<br>
7pd+EG925oHdQ+<u></u>xKXYYVOZK09kLNiQUDE979MmmUkw4D<u></u>oYAKIwJqXGC45MLnk=
Jyz<br>
LVK+UuATk07bs3G5e91w<br>
=3DouEQ<br>
-----END PGP SIGNATURE-----<div class=3D"HOEnZb"><div class=3D"h5"><br>
______________________________<u></u>_________________<br>
wm-spec-list mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">wm-spec-list@gn=
ome.org</a><br>
<a href=3D"https://mail.gnome.org/mailman/listinfo/wm-spec-list" target=3D"=
_blank">https://mail.gnome.org/<u></u>mailman/listinfo/wm-spec-list</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br><div class=
=3D"gmail_signature">=C2=A0 Jasper<br></div>
</div></div>

--20cf307f318878569805108ff9e5--

--===============3600685721809366306==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
wm-spec-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/wm-spec-list

--===============3600685721809366306==--