Why stick with Wincuts

I chose the same project for my Contribution as I did for my Bug Fix because I’m familiar with it. I worked on this project for my bug fix, and the project owner responded to me very quickly. There are several issues in this project that I also have the ability to complete, so I decided to work on Wincuts again for my contribution.

What is Wincuts

Project Website

GitHub Page

WinCuts is a Windows native (via Qt) tool for easily setting up and managing custom keyboard shortcuts. It’s designed for simple usage and is aimed at anyone who wants to save time and increase productivity by using keyboard shortcuts.

How it works

As of now, WinCuts lets you set up custom keyboard shortcuts for running shell/cmd commands that get launched whenever the shortcut is activated. It’s useful if you need to launch specific commands frequently and want to save time by using a keyboard shortcut instead of typing the command every single time. What’s also cool is that none of the shortcuts will go deep enough in your system to cause any damage. They’re all running in the context of the user and are limited to the user’s permissions. And, of course, the shortcuts are only active within the app and hence won’t interfere with any other shortcuts you might have set up (basically, you can’t accidentally override a system shortcut).

Why I picked Wincuts

I chose to contribute to WinCuts because it could improve my productivity when developing on Windows. Since I can fix several issues, I decided to help this project out.

Resources

The project provided both contribution guide, code of conduct and the license this project uses is BSD-3-Clause license. Since this is a relatively new project, there are few participants, but the project’s owner is very active; he can always respond to you within a day, from my experience.

One negative side of this project is the need for more documentation. This does make it difficult to understand the project at the beginning, but since this is a small project and the task I chose to do didn’t interact too much with the main part of the software itself, this didn’t cause too many problems when I was developing.

The Issue

The issue I worked on in this project was Creating a help button inside the app. As the creator mentioned, many users won’t go deep diving to try to find the repository’s README; a simple Help button should work way better. issue

wincutContributeIssue

Contribution process

First, I read the project’s current repository’s README, which contains all the information the user should know in order to use the app correctly.

Then, Start by adding the help button to the main program UI

image

After ensuring that the button is clickable and the user can navigate to the help window when clicking on it, I add information to the window.

image

Finally, I added the feature of clicking on the icon, which also shows the help button. Thus, the contribution has been made.

image

Blocker

During the development, everything went smoothly since I had already contributed to this project before, so I understood how and what I should do. However, I didn’t understand how to use the app in-depth, so I asked other people in the discussion, and the creator quickly answered my question and gave me several suggestions for improvement. image

Pull Request

As of the writing of this blog post, the PR opened was accepted Link to pull request

Conclusion

Overall, I had a good experience working on this issue and project. While the specific problem I chose to work on was pretty simple, this was an excellent experience, and the author put my name on the newest release with credit for my contribution. image