Hi all,

I'm developing KScreenGenie, a new screenshot application that aims to replace KSnapshot. So far the response have been positive, and it's more-or-less functionally equivalent to KSnapshot (except for losing support for grabbing individual widgets in an application and freeform selections). Right now, the only thing that stands between the code and a beta release (yeah, beta, not alpha - it's already pretty stable and totally awesome) is the lack of an icon.

I have absolutely no skills in iconography, so I'm posting here on advice of a few people over at IRC.

The moment I have an icon, I'm going to move from Playground into kdereview, eventually aiming for kdegraphics. The repo is at http://quickgit.kde.org/?p=kscreengenie.git

I'd appreciate any help that I can get!

Cheers,
Boudhayan Gupta

May I ask why KSnapshot should be replaced? One of the best competitive tools of KDE.

Well, it started as a cleanup/refactor operation to clean up KSnapshot so that a) old code relics from the KDE3.5 days are removed (yes, such code still exists in the frameworks branch too) and b) it can eventually easily support Wayland when an API for it becomes available. Over time, I found it easier to just start from scratch and import code from KSnapshot as necessary, so it's written as a KF5/Qt5 app from the very outset. The GUI is even QtQuick 2.0.

Sounds good. But I'd still vote for keeping the old name. If users have to know that KSnapshot is a legacy 4.x product and KScreenGenie is the same tool, updated to 5.x it might be confusing.

From a usability POV the tool is pretty good as it is. What I dislike from time to time is that I close it by escape and need to restart again. Not sure why but it feels like an interruption (cannot try it right now). To improved the situation you could perhaps make it look as it resides in background (e.g. by speeding up and with persistence of setup). If you want to redesign the UI I'd start with the selection of the type of source which is rather slow and concealed due to the dropdown. Furthermore the complete layout should match the HIG for simple UIs [1,2]. And last but not least there is an ongoing discussion about the sendto feature which could be relevant here as well [3].

Sorry for answering questions that haven't been asked. Sadly I cannot provide graphics for you

[1] https://techbase.kde.org/Projects/Usabi ... onPatterns
[2] https://techbase.kde.org/Projects/Usabi ... ndPatterns
[3] https://git.reviewboard.kde.org/r/123342/

Hi Heiko,

You had some very good points, so rather than take a call by myself, I ran this post by the folks over at IRC. They seem to think the following:

1. Keeping the KSnapshot name would be really good if it is possible. I'll talk to the current KSnapshot maintainer about if it is possible to give a brand new application the same name as the old one, and if so how it would be done
2. The UI as it is now has no complaints, but there's a definite possibility that things could improve and also that KScreenGenie could go where KSnapshot has not gone before. So the suggestion is to release early, (right now in its current state) release often and act on feedback from users
3. As for the ongoing discussion about re-organizing the Send-To menu, I've already been in touch with the author of the review request and we're both excited about implementing something like this in KScreenGenie

-- Boudhayan Gupta

I too think that it's better to keep the old name and use the icon that's already there.

IIRC, Aaron is the maintainer of KScreenshot, you should probably talk to him regarding this whole endeavour.

ivan wrote:IIRC, Aaron is the maintainer of KScreenshot, you should probably talk to him regarding this whole endeavour.

Boudhayan (BaloneyGeek) has already talked to Aaron about the endeavor as such on Google+ (though not about the idea of keeping the name). Let's see how Aaron will react to the idea of keeping the name for the rewritten application.