Re: Named/tagged virtual desktops
Martin Graesslin <[email protected]> Thu, 09 Jun 2016 13:40:58 +0200
| Newsgroups | gmane.comp.gnome.wm-spec |
|---|---|
| Message-ID | <2832713.Bz3OWoNnOk@martin-desktop> |
--===============5840652626812589162== Content-Type: multipart/signed; boundary="nextPart2115247.8XKiOfJgFa"; micalg="pgp-sha1"; protocol="application/pgp-signature" --nextPart2115247.8XKiOfJgFa Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" On Thursday, June 9, 2016 7:34:57 AM CEST Yonas Yanfa wrote: > I would love the ability to make use of named/tagged virtual desktops. >=20 > A "named virtual desktop" is a virtual desktop that has a unique title, > like "Work desktop". Each virtual desktop would have only one unique name. >=20 > A "tagged virtual desktop" is a virtual desktop that has been assigned > one or more tags, like "work", "sports", "gnome coding", etc. >=20 >=20 > Here are a few ideas on how applications could make use of them: >=20 > - mail clients (eg. Thunderbird) could load your work email accounts for > your "Work" virtual desktop > - web browsers (eg. Firefox) could load work and sports related > bookmarks for virtual desktops with the tags "work", and "sports", as > well as work-related add-ons for your "Work" virtual desktop > - text editors could use four space indentation for virtual desktops > tagged "gnome coding", and three space indentation for desktops tagged > "personal coding". >=20 >=20 > Tags could be added or removed at any time, allowing you to quickly > customize all applications placed on a virtual desktop without > restarting the applications. >=20 > Tags could be shared across multiple virtual desktops (i.e. they are not > restricted to one virtual desktop). >=20 > Once the API is published, application vendors could add support for > named/tagged virtual desktops, or allow plugin developers to implement > this in their own creative ways. >=20 > The difference between this and Qubes OS is that Qubes OS completely > separates applications into their own "domains" as a security feature. > Named/tagged virtual desktops isn't about security or program isolation > - applications should be able to access the same filesystem, clipboard, > etc, as usual, but simply store and present application data and > preferences uniquely per named/tagged virtual desktop for users that > choose to make use of the feature. >=20 >=20 > Does this appeal to anyone else? >=20 > Has anyone already began work on this? =46rom what you describe that sounds a lot like KDE's Activity concept, see= =20 https://api.kde.org/frameworks/kactivities/html/index.html Cheers, Martin --nextPart2115247.8XKiOfJgFa Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEABECAAYFAldZVcoACgkQqVXwidMiVroVHwCfZsG0DUToMKfapUrFhecQHNzE lIkAnRD+IWLYtxaAUvAWRfKPs6ffANSj =f5gv -----END PGP SIGNATURE----- --nextPart2115247.8XKiOfJgFa-- --===============5840652626812589162== 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 --===============5840652626812589162==--