Skip to content

Email or Generate QSL to Print#995

Open
aa5sh wants to merge 3 commits intofoldynl:masterfrom
aa5sh:EmailQSLCard
Open

Email or Generate QSL to Print#995
aa5sh wants to merge 3 commits intofoldynl:masterfrom
aa5sh:EmailQSLCard

Conversation

@aa5sh
Copy link
Copy Markdown

@aa5sh aa5sh commented Apr 9, 2026

This is something I had a stand alone app developed for but felt like others may like something along these lines so worked to integrate it into QLog. It allows for a QSL Card to be generated that can either be emailed from QLog or saved and printed to be mailed.

aa5sh added 3 commits April 8, 2026 21:47
Implements Email QSL functionality: adds an EmailQSL service (SMTP worker, MIME builder, card rendering and merge-fields), UI for sending and previewing (EmailQSLDialog and .ui), and settings/overlays storage. Introduces a CardEditorWidget component and settings widget for configuring card image/overlays and SMTP credentials (uses secure credential store and QSettings). Tracks sent timestamps in contacts.fields JSON and performs async SMTP operations with STARTTLS/SSL and AUTH support. Wires all new sources, headers and forms into QLog.pro and updates logbook/settings UI to integrate the new feature.
Keep overlay positions, font sizes and box dims proportional when the card background changes and produce smaller email attachments. EmailQSLSettingsWidget: rescale stored overlay pixel values when a new image with different size is loaded; use a 1280px reference width for default fonts/positions and scale horizontal metrics accordingly; add minimum sizes for fonts and box dims. EmailQSLService: render the card at full resolution but scale the exported JPEG to a fixed EMAIL_WIDTH (1280) for email attachments to reduce file size. Also add clarifying comments about how overlay coordinates are stored and used.
@foldynl
Copy link
Copy Markdown
Owner

foldynl commented Apr 10, 2026

@aa5sh Michael, I think this is already beyond what I would expect from a logging application. It’s not feasible to turn QLog into an email client with all the associated configurations.

However, I’ve been thinking about how the idea could be implemented. One option would be for QLog to “prepare” an email and pass it to the default email client, which would handle the sending procedure. I’m not sure how batch sending and similar aspects would be handled, but as I mentioned at the beginning, this is already getting too complex.

@aa5sh
Copy link
Copy Markdown
Author

aa5sh commented Apr 10, 2026

That makes sense I wasn't really sure if this was to far so I understand your hesitation. I know your goal is to keep QLog powerful but streamlined. I would fully support what ever you decide - not a big deal.

@foldynl
Copy link
Copy Markdown
Owner

foldynl commented Apr 10, 2026

Let’s keep it open for now. I’ll try to come up with something around it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants