Skip to main content

Effortlessly monitor and display real-time file access for any process

Project description

jdProcessFileWatcher

Effortlessly monitor and display real-time file access for any process

jdProcessFileWatcher

With jdProcessFileWatcher, you can monitor all the files accessed by a process. It allows you to start any program and observe in real-time which files it accesses through an easy-to-use GUI. Additionally, you have the option to connect to an already running process.

Translate

You can help translating jdProcessFileWatcher on Codeberg Translate

Develop

jdProcessFileWatcher is written in Python and uses PyQt6 as GUI toolkit. You should have some experience in both. You can run jdProcessFileWatcher.pyto start jdProcessFileWatcher from source and test your local changes. It ships with a few scripts in the tools directory that you need to develop.

CompileUI.py

This is the most important script. It will take all .ui files in jdProcessFileWatcher/ui and compiles it to a Python class and stores it in jdProcessFileWatcher/ui_compiled. Without running this script first, you can't start jdProcessFileWatcher. You need to rerun it every time you changed or added a .ui file.

BuildTranslations.py

This script takes all .ts files and compiles it to .qm files. The .ts files are containing the translation source and are being used during the translation process. The .qm contains the compiled translation and are being used by the Program. You need to compile a .ts file to a .qm file to see the translations in the Program.

UpdateTranslations.py

This regenerates the .ts files. You need to run it, when you changed something in the source code. The .ts files are contains the line in the source, where the string to translate appears, so make sure you run it even when you don't changed a translatable string, so the location is correct.

UpdateUnixDataTranslations.py

This regenerates the translation files in deploy/translations. these files contains the translations for the Desktop Entry and the AppStream File. It uses gettext, as it is hard to translate this using Qt. These files just exists to integrate the translation with Weblate, because Weblate can't translate the Desktop Entry and the AppStream file. Make sure you run this when you edited one of these files. You need to have gettext installed to use it.

UpdateTranslators.py

This uses git to get a list of all Translators and writes it to jdProcessFileWatcher/data/translators.json. This is used to display the translators in the About Dialog. You need git to run this script.

WriteChangelogHtml.py

This read the Changelog from deploy/page.codeberg.JakobDev.jdProcessFileWatcher.metainfo.xml, converts it to HTML and writes it to jdProcessFileWatcher/data/changelog.html. This is used to display the Changelog in the About Dialog. You need appstream-python to be installed to use this script.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

jdProcessFileWatcher-1.1.tar.gz (220.1 kB view details)

Uploaded Source

Built Distribution

jdProcessFileWatcher-1.1-py3-none-any.whl (233.0 kB view details)

Uploaded Python 3

File details

Details for the file jdProcessFileWatcher-1.1.tar.gz.

File metadata

  • Download URL: jdProcessFileWatcher-1.1.tar.gz
  • Upload date:
  • Size: 220.1 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/4.0.2 CPython/3.12.1

File hashes

Hashes for jdProcessFileWatcher-1.1.tar.gz
Algorithm Hash digest
SHA256 2cc35fc614afc1ca8b45f8f848a23291b9ec1604d1dd637b47e7408bfdbaf728
MD5 e9f50fea04ee005aa3ec3c645d3f8adf
BLAKE2b-256 fc15470080adbbc8c4872f0b76cf1f0be7ba0fa073b78300db98adb3b0f945f5

See more details on using hashes here.

File details

Details for the file jdProcessFileWatcher-1.1-py3-none-any.whl.

File metadata

File hashes

Hashes for jdProcessFileWatcher-1.1-py3-none-any.whl
Algorithm Hash digest
SHA256 160e01971551ed484e370919ed211720b46b36d8c2020a0028e1d2c6b13190df
MD5 77bfe130f4ddc712182d6cf4d7c51a48
BLAKE2b-256 79f65d4cdf0c0d3465eac4b78e1ec32a753321ca0c328a1a5ac9e019a2457ca2

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page