1. Very Good

According to our research a lot of KGet users consider browser integration to be essential. Offering users the opportunity to enable Konqueror integration right from the start is a good idea. However this also poses a few - solvable - problems. See below.

2. Not So Good

2.1 Drop target stuck in konqueror integration question (solved)

Severity: low

First time use of drop target (together with first time use of KGet overall) shows the target in the center of the screen. Trying to drag it where needed fails since it’s stuck in the middle. This leads to confusion. The reason why the drop target can’t be interacted with seems to be the first-usage information. KGet has opened a small modal dialog in the background where the user has to decide about Konqueror integration. Only technology savvy users will be able to make the connection between the modal dialog and the drop target being unresponsive.

Suggestion: Is there a way to make the drop target responsive even if the modal dialog is not dismissed yet? The drop target should not be tied to the browser integration decision.

2.2 Better wording of dialog buttons (solved)

Severity: medium

The “first start” dialog shows three buttons: enable, do not enable and cancel. But the text message above the buttons does not contain the word “enable”.

Suggestion: It would be more consistent to reword the message to contain the word “enable”, so users will quickly recognize what the buttons are about. For example “Would you like to enable KGet as the download manager for Konqueror?” (instead of “use”).

2.3 Add drop down arrow to “download manager” button (pending kdelibs change)

Severity: medium

In Konqueror toolbar: click on download manager - drop down appears, but was unexpected (it’s a click button, expected was the launch of the download manager)

Suggestion: Add the customary down arrow for dropdowns to the icon to make the button consistent and so users know what to expect.