Originally posted by Michal198569 May 6, 2026
Hi Allsky Team,
I've been testing the new custom notification image feature using the myFiles/notificationImages directory. While it works well, I noticed one major drawback for average users: creating and maintaining 12+ separate image files manually is quite difficult. If someone later wants to change the background, font style, or add translations, they must recreate every image again from scratch.
Because of this, I experimented with modifying generateNotificationImages.sh into more of a dynamic template engine, and I believe this approach could significantly improve the notification system in the future.
Advantages of the Template Approach
No Manual Image Editing
Users would only need to provide a single background image instead of creating every notification individually in a graphics editor.
Automatic Rendering
The script dynamically handles:
- text placement
- font scaling
- colors
- overlays
Easier Localization
I added support for a secondary language parameter, allowing all notification images to be translated automatically at once.
Proposed WebUI Integration
Instead of requiring users to edit files manually or modify Bash scripts, this could eventually become a simple WebUI feature:
- Upload one background image
- Translation table for localized strings
- Font size and Y-position sliders
- Live preview of the generated image
- One-click "Generate" button
The system would then automatically generate all required notification images into the correct directory.
I believe this would be much more user-friendly than the current myFiles workflow and would allow users to create professional-looking localized notifications without needing terminal access or graphics editing skills.
About My Prototype
I managed to create a working proof-of-concept by adapting the original script with the help of AI tools. The dynamic rendering, background layering, and dual-language support are already functional on my station.
However, I'm mainly sharing this as inspiration for the official developers. My implementation is only a hobby project and not production-quality code, but I believe the overall concept could be a valuable direction for Allsky in the future.
Attachments
I'm attaching several examples generated by my modified script (StartingUp.jpg, DarkFrames.jpg, Error.jpg, etc.). The custom backgrounds and dual-language support significantly improve the visual appearance and readability.
>
>
>
>
I'm also attaching a simple UI mockup showing how a future "Notification Image Editor" could look inside the WebUI.
Features shown in the mockup:
- Live preview
- Translation table
- Visual font/position controls
- One-click deployment
I'm just a hobbyist and tinkerer, but I hope these examples help demonstrate why this could be a useful addition to Allsky in future releases.
Discussed in #5154
Originally posted by Michal198569 May 6, 2026
Hi Allsky Team,
I've been testing the new custom notification image feature using the myFiles/notificationImages directory. While it works well, I noticed one major drawback for average users: creating and maintaining 12+ separate image files manually is quite difficult. If someone later wants to change the background, font style, or add translations, they must recreate every image again from scratch.
Because of this, I experimented with modifying generateNotificationImages.sh into more of a dynamic template engine, and I believe this approach could significantly improve the notification system in the future.
Advantages of the Template Approach
No Manual Image Editing
Users would only need to provide a single background image instead of creating every notification individually in a graphics editor.
Automatic Rendering
The script dynamically handles:
Easier Localization
I added support for a secondary language parameter, allowing all notification images to be translated automatically at once.
Proposed WebUI Integration
Instead of requiring users to edit files manually or modify Bash scripts, this could eventually become a simple WebUI feature:
The system would then automatically generate all required notification images into the correct directory.
I believe this would be much more user-friendly than the current myFiles workflow and would allow users to create professional-looking localized notifications without needing terminal access or graphics editing skills.
About My Prototype
I managed to create a working proof-of-concept by adapting the original script with the help of AI tools. The dynamic rendering, background layering, and dual-language support are already functional on my station.
However, I'm mainly sharing this as inspiration for the official developers. My implementation is only a hobby project and not production-quality code, but I believe the overall concept could be a valuable direction for Allsky in the future.
Attachments
I'm attaching several examples generated by my modified script (StartingUp.jpg, DarkFrames.jpg, Error.jpg, etc.). The custom backgrounds and dual-language support significantly improve the visual appearance and readability.
I'm also attaching a simple UI mockup showing how a future "Notification Image Editor" could look inside the WebUI.
Features shown in the mockup:
I'm just a hobbyist and tinkerer, but I hope these examples help demonstrate why this could be a useful addition to Allsky in future releases.