Zettlr: [ENHANCEMENT] Make update notification non-obstructive

Created on 10 Aug 2020 · 3Comments · Source: Zettlr/Zettlr

Description

It is nice to be notified about new releases and I like it, but I would like it to be non-obstructive.

Proposed Changes

Make the pop-up smaller.
Show an icon that denotes a fix for a critical bug. (So that I can update it quickly)
The notification should not obstruct the user.

Caveats

The adoption of the new update will be slower if the update. (A possible solution is to create a self-updating app)

Additional Information

If this problem is already present kindly point me at it.

UX enhancement mid

Source

tupio

Most helpful comment

I do see that! The reason the update notification is that "in ya face" is because I want to minimize the people using older apps opening issues here and thereby reduce the workload. Maybe a self-updating app would be the easiest, but it's quite something to set up … however, I'm considering replacing the update notification with a visible button in the toolbar

nathanlesage on 10 Aug 2020

👍3

All 3 comments

Thanks so much for opening up your first issue here on the repository! 🎉 We would like to warmly welcome you to the community behind the app! ☺️ We'll check in soon and have a look at your issue. In the meantime, you can check your issue and make sure it aligns with our contribution guidelines! Here's the comprehensive list:

Enhancements

An enhancement takes a feature and improves or alters its behaviour. Please make sure to argue how your proposition will aid non-technical text workers, and why it can't be emulated easily with other features or apps!

Feature requests

Feature requests introduce whole new features into the app. This requires a lot of work, so these might be turned down if the implementation costs supersede the benefits we expect to see from implementing it. Please do not be disappointed if that happens. It likely has nothing to do with your great request but simply with us and our missing resources!
You can of course always ask someone to implement this feature, because a PR with a working new feature has much higher chances of being merged! :)

Bug reports

Please note that one of the main reasons for why bug reports cannot be addressed is that there's not enough information for us to find and fix the bug you describe, so make sure you try to pinpoint the bug as close as possible.
The ideal bug report for us has two qualities:

The bug is always reproducible, at least within a certain context. 2. We know exactly what specifically goes wrong, and there is consensus on
what should happen instead.

Please note that if you encounter behaviour that does not align with your expectations of what would happen, this might as well be simply intended behaviour and we need to simply _clarify_ why the behaviour is the way it is. This is not to be considered a bug and such issues may be closed! Suggest an enhancement instead!
But now, have a great day and thank you again!