Replies: 1 comment 1 reply
-
|
This is a lovely writeup, but the main issue with doing this is that it is a lot of logic to implement and maintain for future releases that YaLTeR will have to do. Please note this is my opinion thanky |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Having created hundreds of screenshots over the years with Flameshot, I'd say these concepts are really important IMO and the current screenshot solution we have today does not handle them. Niri does so many things amazingly well and I wonder if there's an opportunity to beef up the screenshot utility to be best in class without compromises.
While moving away from Flameshot, I ended up in a situation of cobbling together custom scripts and tools to try and get them captured in a few different ways but it's a frankenstein shell script approach of grim, slurp, the niri screenshot tool and satty. The end result is it's worse than Flameshot due to limitations of these tools individually.
Capture modes:
Saving:
Annotating:
Ease of use:
Beta Was this translation helpful? Give feedback.
All reactions