qtimgren
Description
This is a GUI around the pyimgren package. Currently, it is able to rename camera images via pyimgren forth and back. Its main feature is that it allows a manual selection of the images to rename.
Of course buttons are there to allow default selections.
It is based on profiles. For qtimgren, a profile is what is required for
pyimgren configuration:
- a folder
- a source pattern to identify camera images (typically IMG*.JPG or DSCF*.JPG)
- a compatible with
datatime.strftimepattern to build the new name from the JPEG timestamp - and of course a unique name
Thanks to pyimgren, it is possible to use a delta in minutes to cope with a digital camera having a wrong time.
In order to make image selection easier, thumbnails can be displayed in the main application window along with the current, future and original names. But as image computation and display are expensive tasks, the display can be turned off. Anyway, the computation is asynchronous, meaning that the application can be used as soon as the currently displayed images are available. Starting with the 0.5.x series, thumbnails are statically cached in a local SQLite database.
Installation
Direct installation on Windows
Thanks to PyInstaller and InnoSetup, an installer and a portable zip file are available on GitHub.
That way you have no dependencies, not even on Python.
From PyPI
pip install qtimgren
From GitHub
This is the recommended way if you want to contribute or simply tweak
qtimgren to your own requirements. You can get a local copy by
downloading a zipfile but if you want to make changes, you should
rather clone the repository to have access to all git goodies:
git clone https://github.com/s-ball/qtimgren.git
You can then install it in your main Python installation or in a venv with:
pip install -e .
or on Windows with the launcher:
py -m pip install -e .
Special handling of version.py:
QtImgren relies on hatch-vcs to automatically extract a
version number from git metadata and store it in a version.py file
for later use. This requires the availability of both git (which should
not be a problem when the project is downloaded from GitHub), and
an installation via pip or a build through a PEP518 compatible tool.
If it fails because one is not available or because
git metadata is not there (if you only downloaded a zip archive from
GitHub), the version is set to 0.0.0
For that reason, if you do not use git to download the sources, you
should download a source distribution from PyPI, because the latter
contains a valid version.py
pip uses the pyproject.toml file with respect to PEP-518 and
PEP-517 to know that hatch-vcs is required before the build.
Basic use
Once installed, you can run the application:
qtimgren
Internationalization
The application is natively written is English, and contains a French
translation of its IHM. It depends on Qt Linguist tools for generating the
binary file used at run-time. This is automatically done at build or install
time by the hatch-pyside project.
Of course, if you install from a PyPi wheel, the compiled message files are included as a resource.
At run time, the system default language is used by default, or can be
explicitly specified with the --lang option:
qtimgren --lang=fr # forces fr language
qtimgren --lang=C # forces native english language
Contributions
Contributions are welcome, including translations or just issues on GitHub. Problems are expected to be documented so that they can be reproduced. But I only develop this on my free time, so I cannot guarantee quick answers...
Disclaimer: beta quality
All functionalities are now implemented, and the underlying pyimgren module has been used for years. I trust it enough to handle my own photographs with it. Yet it still lacks a decent documentation, and has not been extensively tested
License
This work is licenced under a MIT Licence. See LICENSE.txt
Metadata
Release files for qtimgren 0.5.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| qtimgren-0.5.2.tar.gz | 8.8 MB | Without provenance | Details for qtimgren-0.5.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qtimgren-0.5.2-py3-none-any.whl | Python 3 | none | any | Details for qtimgren-0.5.2-py3-none-any.whl |
Total release size: 8.8 MB
Release files / qtimgren-0.5.2.tar.gz
| Download URL | qtimgren-0.5.2.tar.gz |
|---|---|
| Size | 8.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1c0630d60ee9ffa8829346608cc122e35853c1f196be79de92edf47c33acefc6
|
|
BLAKE2b-256 checksum How to use checksums |
c7cea0f42ebddc7ec4c4b73a8c743fc28bf42e338188c1fe0d3fb13c0e0bb489
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.28.1
|
Release files / qtimgren-0.5.2-py3-none-any.whl
| Download URL | qtimgren-0.5.2-py3-none-any.whl |
|---|---|
| Size | 45.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
022dc0c42fb48408d807eff68529ebbeba53ef18ae72a211e1ff07e6a4176591
|
|
BLAKE2b-256 checksum How to use checksums |
d23ca3a683a7922c21a7d6b98503592a4b4b1fedc2220657ac561cf41411ed76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.28.1
|
Security for qtimgren 0.5.2
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.