Skip to main content

Plover Application Dictionary

Plover dictionary entries based on the current focussed application.

This plugin has two dictionary types .ad and .mad, for defining single or multiple application dictionaries respectively. The first is not readonly, allowing for entries to be added through Plover, but .mad dictionaries are readonly. Both have to be edited to change which applications the entries within the dictionary

Installation

  • Navigate to the installation directory for Plover and open a terminal / command prompt.

  • Run: <exe_name> -s plover_plugins install -e plover-application-dictionary

    The plover-application-controls plugin should be installed automatically as a dependency.

  • Restart Plover.

  • Configure > Plugins > Enable application_controls.

Disabling application_controls will prevent the plugin from being able to detect the currently active window.

Dictionaries:

Dictionaries can match applications using three properties, app, class and title. title should be consistent between platforms, whereas class and app will depend across platforms and specific user installations. To find an application's app or class, see plover-application-controls meta actions. class is only available on some Linux systems.

Matching supports full Regex. An empty string will match anything.

The following is an example dictionary which only activates when Discord or Firefox is active. Implementation from system to system may vary.

Example.ad:

{
  "app": "",
  "class": "discord|Navigator",
  "title": "",
  "entries": {
    ...
  }
}

The following is an example dictionary which defines separate entries depending on the user being messaged on Discord.

Example.mad:

[
  {
    "app": "",
    "class": "discord",
    "title": "@User1 - Discord",
    "entries": {
      ...
    }
  },
  {
    "app": "",
    "class": "discord",
    "title": "@User2 - Discord",
    "entries": {
      ...
    }
  }
]

Metadata

Release files for plover-application-dictionary 2.0.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for plover-application-dictionary 2.0.3
File Size Uploaded Provenance Actions
plover-application-dictionary-2.0.3.tar.gz 15.7 kB Without provenance Details for plover-application-dictionary-2.0.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for plover-application-dictionary 2.0.3
File Interpreter ABI Platform Actions
plover_application_dictionary-2.0.3-py3-none-any.whl Python 3 none any Details for plover_application_dictionary-2.0.3-py3-none-any.whl

Total release size: 32.8 kB

Release files / plover-application-dictionary-2.0.3.tar.gz

Download URL plover-application-dictionary-2.0.3.tar.gz
Size 15.7 kB
Tags Source
SHA-256 checksum
How to use checksums
7585c58328251f11a6c11f46b3226dd99b793c629d369699a3e1ec09dffd2bf2
BLAKE2b-256 checksum
How to use checksums
a587a67df739a935872fb8b5a7e819cc4fc9d3d8de83446b67700ad523448156
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.11.1

Release files / plover_application_dictionary-2.0.3-py3-none-any.whl

Download URL plover_application_dictionary-2.0.3-py3-none-any.whl
Size 17.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fa16ace202e6a23d714e7d6172c4b0c84ace1aa29400203fa12308b14f795b6b
BLAKE2b-256 checksum
How to use checksums
36afc2e5b595e8460e4e66bb5a43be9680791fa899300c12b8649b9f6fb201fc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.11.1

Security for plover-application-dictionary 2.0.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page