hakutaku/tdesktop
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

init
Some checks failed
Docker. / Ubuntu (push) Has been cancelled
Details
User-agent updater. / User-agent (push) Failing after 15s
Details
Lock Threads / lock (push) Failing after 10s
Details
Waiting for answer. / waiting-for-answer (push) Failing after 22s
Details
Needs user action. / needs-user-action (push) Failing after 8s
Details
Can't reproduce. / cant-reproduce (push) Failing after 8s
Details
Close stale issues and PRs / stale (push) Has been cancelled
Details

Browse Source
This commit is contained in:
allhaileris
2026-02-16 15:50:16 +03:00
commit afb81b8278
13816 changed files with 3689732 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
Telegram/ThirdParty/xdg-desktop-portal/doc/reasons-to-use-portals.rst vendored Normal file
View File

@@ -0,0 +1,26 @@
Reasons to Use Portals
======================
Using XDG Desktop Portal brings major advantages over writing desktop-specific
code for app developers:
* **Strict sandbox**: portals enable sandboxed apps to access a curated set of
features from the desktop environment and the host system, without weakening
the sandbox of the app.
* **Unified code**: by using portal APIs, apps only need to write a single
desktop-agnostic code that runs on a variety of desktop environments. Portals
can be used by sandboxed and unsandboxed apps alike. App developers are
encouraged to use portal APIs even for unsandboxed apps.
* **Seamless integration**: portal backends provide cost-free integration with
the desktop. For example, simply using the :ref:`File Chooser portal<org.freedesktop.portal.FileChooser>`
will make apps use the file picker dialog native to the desktop environment
they're running on.
* **Permission system**: portals can restrict access to system resources through
a permission system. Permissions can be granted, revoked, and controlled
individually by the end user. This gives end users more control over apps.
In addition to the reasons above, some desktop features are primarily - and
sometimes exclusively - available through portals. For example, the primary way
of capturing screens and windows on Wayland desktops is through the
:ref:`ScreenCast portal<org.freedesktop.portal.ScreenCast>`, and some desktop
environments don't even expose other means to capture the screen or windows.