Comments are not wrapped, even though the line has proper height.

The GUI should inform the user when no packages are not added to the 'list' (or to be precise none are put into the bodhi_worker queue). This might be caused by several possibilities (as the code is now)

packagesworker.py

    def load_installed(self, releasever):
            ...
            if installed_timedelta < installed_max_days:
                if rel.startswith('fc') and releasever in rel:
                    if pkg.ui_from_repo == '@updates-testing':
                        self.bodhi_workers_queue.put(pkg)
                        print "putting to queue", pkg

1. no packages were installed in the last installed_max_days days
2. no packages from the selected release are installed
3. no packages from @updates-testing are installed

I'd suggest altering the logic a bit (pseudocode):

    def load_installed(self, releasever):
        ...
        _updates_testing = False
        _max_days = False
        _releasever = False
        ...
            if pkg.ui_from_repo == '@updates-testing':
                _update_testing = True
                installed_timedelta = now - installed
                if installed_timedelta < installed_max_days:
                    _max_days = True
                    if rel.startswith('fc') and releasever in rel:
                        _releasever = True
                        self.bodhi_workers_queue.put(pkg)
                        print "putting to queue", pkg

So we can inform user via GUI, that no packages are shown since

1. he has no packages from @updates-testing installed (propse a check whether updates-testing is even enabled)
2. no packages were installed in last X days
3. no packages from selected release are installed (check the actual release?)

We are unable to break line in comment.

Since you're the one mostly developing this program now (I assume), the following page is outdated:

https://fedoraproject.org/wiki/Fedora_Gooey_Karma

Please take care of that, because it's the first result when you google up the project name. Make sure it contains up-to-date information or at least redirect to up-to-date information.

Thanks.

I have no idea what "Available" button means, but my left list is empty when I click on that button. I think this is somehow related to issue #13. It doesn't matter which packages are installed from which sources. What matters is the current list of packages in updates-testing in Bodhi.

So, unless I miss something, the Installed/Available buttons should be removed.

After checking the "karma not submitted" checkbox, the respective packages are hidden, as exepected. But when I uncheck the checkbox, the list of packages is not updated, and the only way to re-fill it is to click on "Load Packages" button.

After clicking on "Load Packages" button, the status bar says:
"All installed packages has been loaded. [Fedora 1]"
It should read (i.e.):
"All installed packages has been loaded. [Fedora 19]"

fedora-gooey-karma.py:
    ...
    def __save_installed_pkg_list(self, pkg_object):
-        message = "All installed packages has been loaded. [Fedora %s]" % pkg_object[0]
+        message = "All installed packages has been loaded. [Fedora %s]" % pkg_object

When I want to mention a package NVR, I need to be able to copy its NVR to my clipboard. f-g-k doesn't allow me to do that. In none of the 4 places I see it mentioned I'm not allowed to copy the NVR to my clipboard.

Please allow that. At least the header text should be made selectable.

Please scroll the log (widget at the bottom of the app) from top to bottom, rather than from bottom up. It's much more readable that way.

fedora-easy-karma tells me how long ago I installed the package (e.g. 5 days ago, etc). That's a very important information, because I can then assess whether I have seen any problems with that program in the last X days or not. If I don't have the information, I can't decide properly - for example I know that I used that program 3 days ago and it worked great, but I don't know whether the update was installed before that day or after it.

Please display this information visibly somewhere.

At the moment I need to select a package update on the left side of the app, and then go to the very right side of the app and switch to Comments section. That is very inconvenient (and also very hardly discoverable).

It should be differently. Either all of those could be collapsible sections inside the main pane (similarly to the start tab)

or maybe they could be moved to the top of the main pane and displayed as buttons.

Just some ideas. I'm sure there are even better ones available.

It might be useful to be able to sort the comments in the list, so I can easily see all the negative/positive karma on one place instead of scrolling through all the entries.

The newlines are consumed:

When I click on a package update, I don't see Bodhi comments right away. But I need to see them to be able to test properly. The comments might contain important information what to re-test (-1 karma from some people), or the comments might contain information which program parts were already tested enough and I might decide to test different parts. Or I can learn that this update is totally broken and I don't need to spend my time on it.

The comment section should be displayed on the front page, instead of a second tab. It can be somewhat lighter - for example you could filter out all automated messages from bodhi/autoqa/etc.

I know that there's limited space on the screen. I think that "Yum Info" and "Bodhi Info" sections can be removed from the front page. They are not generally useful and can be part of some "Detailed info" tab. The "Bugs" section occupies a lot of space and could be displayed much lighter. Also it could be displayed only when some bugs are available. The same applies for "Test cases" section.

If you modify these other sections, I think you can fit Bodhi comments right to the front page quite easily.

When sending a karma value, I scroll the mouse wheel up on the karma drop-down list to select +1 karma. But I receive -1 karma instead. That is very weird. Direction up should be connected with positive values, and direction down with the negative values, don't you think?

Please re-order from

-1
0
+1

to

+1
0
-1

Also, please consider using radio buttons instead of the drop-down list. It's easier to click once than to click twice to select the value. Also, it could be some nice buttons (big ones, to hit them easily) with emoticon faces on them.

By default, no karma value should be selected, that will make sure the user won't forget the change the value from the previous update.

When I click Send Karma, nothing happens. Then nothing happens. Then I wonder - have I clicked the button? Should I click it again? Then I wait for more eternity. Then I'm instantly switched to a different update.

Please display some indicator that karma value is being sent. Indefinite progress bar, spinner, something. Also, make sure I can't send the comment twice by mistake.

When it's done, switch me to a next update, but make display a green checkbox next the to just-commented update in the left package list? So that I can be sure the comment was sent successfully and I don't need to go back and check.

There is some info here:
https://blaskovicbranislav.wordpress.com/fedora-gooey-karma/

But if the person arrives at github, there's no info how to run the program.

Please include instructions how to clone the program, install dependencies in Fedora and run the program directly in the README.

Something's wrong, I don't know what. It looks ugly as hell now.

When downloading srpm package, it is downloaded such as:

perl-Pod-Usage-1.66-1.fc21

So the "src.rpm" suffix is missing.

When I try to open an update in a web browser, I see this:

Traceback (most recent call last):
  File "/home/kparal/devel/fedora-gooey-karma/src/browser.py", line 50, in show_bodhi_update_in_browser
    update = self.main.get_bodhi_update()
  File "/home/kparal/.local/bin/fedora-gooey-karma", line 477, in get_bodhi_update
    return pkgList[self.ui.pkgList.currentItem().text()]
AttributeError: 'NoneType' object has no attribute 'text'

In the About dialog inside the program, there is no contact information. No homepage, no link to report bugs, nothing. Please add that, if you want some feedback from your users.

Thanks.

When I move my mouse over a bug title in the Bugs section, I would like to see the full title in a tooltip. Having to resize the window is annoying.

The start tab says:

If you are not sure what you should test, wait until all packages are loaded and see sections below this text.

But most of the packages are not displayed in the tabs below, because the programs are not running neither they have negative karma. The list of packages to test is on the left. The text should be updated to explain that better.

It should be possible to resize the "views" (description/bugs/...) manually.

If "comments" cell contains text with multiple lines, the other fields are vertically aligned to the middle. IMHO it would be better to set vertical alignment to the top.

If I run f-g-k, only one package is available for feedback.
meanwhile-1.1.0-12.fc19

When I run f-e-k, three packages are available for feedback.
fros-1.0-4.fc19.noarch
meanwhile-1.1.0-12.fc19.x86_64
opencv-core-2.4.6.1-1.fc19.x86_64

That means f-g-k detects it wrong. My suspicion is that it doesn't ask Bodhi at all, the reload is too quick. That would be wrong. You can't just load packages from disk and see which ones were installed from updates-testing in the last 7 days. Some of them might have already been pushed stable, and they would be displayed redundantly. Some packages might have be installed 2 or 3 weeks ago, but they can still be in updates-testing, so they would be missing from f-g-k. Some packages could have been downloaded and installed manually, without using a repository. Those would also be missing.

I see no other way than to ask Bodhi on start, similarly to what f-e-k does.

At the moment, browser (new tab in browser) is opened as a reaction to (probably) on_click event of the Testcases/Bugs lists. I'd consider either making visually clear, that these are hyperlinks which will open the browser, or handling double-click event instead of a single-click.