QApt and Muon 0.4 (1.0 beta)

Two weeks after alpha 2, the betas of both QApt and Muon are released. Both are now feature and string frozen for 1.0, and the focus for this release and all releases on towards 1.0 (scheduled for 2 weeks from now) will focus on fixing bugs as they are found. Here’s what has changed:

QApt 0.4.0:

  • A minor optimization in PackagePrivate::searchPkgFileIter(). Should speed up the generation of the changelog url for Package::changelogUrl()
  • Minor optimizations in Package::name(), Package::section(), and Package::component() by constructing less unnecessary temporary QStrings. Shouldn’t be too noticeable, but hey.😉
  • Fixed a crash that occurred when a standards-non-compliant package that lacked a package section was present in the system. (Bug 245177)
  • Reduce RAM usage (heap) by 1.3 MiB by not caching the default candidate version in the Package object. It is cheap to calculate it on-the-fly and does not justify the amount of memory caching it was taking up.
  • Add the Backend::packageForFile() function that enables looking up a Package by a file it installs
  • Fix another encoding bug in the QApt Worker caused by not explicitly converting from UTF-8. It should be the last of those, though.
  • For qapt-batch, use a KMessageBox::detailedError for presenting our queued errors, since the text isn’t selectable in KMessageBox::errorList.
  • Fix a bug in the QApt Worker where it would not report valid progress. (Applications would have blank progress bars) This happened because when I added support for handling fractional percentages (e.g. 60.5% -> 61%), I accidentally made it so that normal percentages would not be handled, making operations reporting fractional percentages be the only ones that would work.

Muon 0.4.0

  • Fix a bug that allowed the items in the Filters sidebar to be editable, due to questionable defaults for QStandardModelItem.
  • Do not report an error if the user cancels the opening of a markings file.
  • Improve the vertical centering of the “Status” and “Requested” columns of the PackageView. Now it’ll be centered for all font sizes, rather than just my own.😉
  • Use a KMessageBox::detailedError for presenting our queued errors, since the text isn’t selectable in KMessageBox::errorList.
  • Let software-properties-kde handle reloading the package lists after it edits them, since you already have to give your password to open it, and having to give it again to reload inside muon is annoying.

Packages are building in the usual place and should be available within the day. Sources for QApt and Muon can be found here and here, respectively. A new snapshot of libdebconf-kde should also be available, as Daniel has made a few nice improvements since the first snapshot.🙂

Things are shaping up for release. I’m quite happy. I am leaving this Friday for vacation, and will return August the 11th. I will, however, try to find the time to do a release candidate for QApt/Muon a week from today. A week after that, 1.0 final will be released, so please, test it and file those bug reports!🙂

I’ll blog about my cryptic blog last night in a bit, so stay tuned.😉

30 Responses to QApt and Muon 0.4 (1.0 beta)

  1. Ignazio says:

    Thank you Jonathan.
    This is a great great great work!
    I believe in Muon🙂

    • Electron says:

      I believe in God. And free beers. And aliens, occasionally. But I’ll follow Muon from the beginning, to watch it grow, and finally replace God. Or just KPackageKit. I’m not drunk. And thank you!

  2. d2kx says:

    I’m not all that excited. Not because of the actual software, it’s probably great and replaces KPackageKit easily. But it is not the missing piece Kubuntu needs, meaning a kind of replacement to the Ubuntu Software Center, an application for casual users to install software. A package manager like this one (or like Synaptic) is not very friendly for casual users and more advanced users often just use apt-get anyway (I know I do).

    • Niko says:

      I have to disagree with you, synaptic is way more user friendly than Ubuntu Software Center (I am so happy that Kubuntu does not have it).

    • gp says:

      I agree with d2kx.
      Muon is great (probably will be the best) but is a software managare like Synaptic, that is for power users.
      This is not a replacement to the Ubuntu Software Center.
      Muon or Synaptic are very hard for a casual user. i.e., If a casual user wants search Firefox expects to find only the application (or applications) and not dependencies and other packages related with firefox.
      This is frustrating for casual users.

      • And I agree too. I’ve always planned to write a Software Center-like frontend utilizing QApt after Muon has a stable release. But since as of yet KPackageKit has not provided a way to administrate all of the basic aspects of package management, a full-featured frontend such as Muon was also vital.

  3. takanowaka says:

    great work so far.. are there any plans for making it available (packaging) for debian squeeze?

    • The source packaging should build with no changes in a sid environment, though I don’t think the binary packages from the PPA are usable. I don’t have a Debian system available to me, so I don’t think that I will be able to provide packages personally.😦

  4. SONA says:

    Stupid question (?):

    Can I install QApt and Muon alongside KpackageKit, to try it?

  5. gp says:

    @Jonathan Thomas:
    >And I agree too. I’ve always planned to write a
    >Software Center-like frontend utilizing QApt after
    >Muon has a stable release.
    >
    Oh, this is fantastic. I didn’t know it.

    >But since as of yet KPackageKit has not provided a
    >way to administrate all of the basic aspects of
    >package management, a full-featured frontend such as
    >Muon was also vital.
    >
    100% right!

    Good Work😉

  6. frank says:

    Is this software centre thingy a (k)ubuntu-only thing? I’d rather Muon becomes the one-to-rule-them-all for _all_ apt-based distros. Now that I found out how to checkout from KDE svn, it compliled without any problems on Squeeze. Thanks for fixing the double-click thingy in the categories view, now I can really use muon.

    Using said categories lists now, it came to my attention that the vertical tabs indeed aren’t an optimal solition. I have a 1400×1050 monitor, where continuous switching between different categories and filters means a lot of mouse-prodding. I can’t offer a sound alternative though.:-/

    • The potential software-center would not be kubuntu-only.😉

      And yeah, the current usage of vertical tabs is not optimal. (The widget is a bit ugly on all themes) But, like you, I’ve been unable to think up a better alternative.😦

      • Luis says:

        Why don’t you juse use regular tabs? Or a dropdown menu?

        Thanks for muon and Qapt.

      • Regular tabs would be a bigger waste of space, really, and dropdown menus aren’t good for large amounts of items. At the least, it’s better than Synaptic’s awful pseudo-vertical tabs, which have visually disconnected buttons that change what the view shows. (It took me forever to figure out what they did)

      • Luis says:

        Mmm, three items isn’t many items. Also, you’re axiomatically wrong😄, dropdown menus ARE designed for long lists (I just mean a dropdown menu to replace the current tabs, not the tab content, just a dropdown menu up there with the 3 options).

        Other option, more original, but coherent with the KDE desktop, could be using a breadcum navigation style.

      • The only list that could have 3 or less is the Origin filter list. Using combo boxes (dropdown lists) violates several parts of the KDE HIG: http://techbase.kde.org/Projects/Usability/HIG/Combo_Box

        Namely, selecting combobox items should not initiate an action (such as filtering, in this case) Also, since we do not know the precise amount of items each filter can have, a list box as is currently used is proper. Furthermore, a breadcrumb navigation is really only mean for hierarchical navigation, and currently you can really only go one layer deep with filters. (There are no subfilters)

        Believe me, alternatives to the vertical tabs have been considered.

      • Luis says:

        “The only list that could have 3 or less is the Origin filter list”

        And it’s the only place where it’s needed, since it’s only meant to replace the vertical tabs. The rest could be displayed just as it’s being displayed.

        “Namely, selecting combobox items should not initiate an action (such as filtering, in this case)”

        In any case, if the HIG are suggesting vertical tabs as a better option, then the HIGs are wrong, no the other way around. Have you ever seen a well designed GUI using vertical tabs?

        “Also, since we do not know the precise amount of items each filter can have, a list box as is currently used is proper.”

        When I said “Why not dropdowns” I didn’t mean for all the elements, just instead of the vertical tabs (which are also wasting space).

        “Furthermore, a breadcrumb navigation is really only mean for hierarchical navigation, and currently you can really only go one layer deep with filters. (There are no subfilters)”

        This is a design error, there’s no reason why “mail”, “web browsers”, etc aren’t under a set called “Internet”. Same for multimedia applications and so on. Navigation becomes a hell lot easier if it’s well structured.

  7. diego says:

    Keep up the good work, you’re doing great stuff!

  8. gp says:

    But is not still build Muon package ?

  9. Praveesh K P says:

    Try searching using the keywords “notification osd” . muon will not give any result while synaptic will show the package notify-osd package which is used in Ubuntu for notification . This is just one example

    Just telling to help you improve the searching in muon.

    For NOW synaptic is better in searching . I am sure it will improve in muon

  10. SONA says:

    I’ve tried v0.4 shortly, there are two things that disturb me:

    1. It seems that Muon don´t respect the existing policykit settings. I must enter a password for everything, it would be nice when Muon simply takes the existing policykit setting.

    2. A click on a packagename opens the “Information-Window” at the bottom, but there is no possibility to close it again. I miss a tiny close button [x], and additionally the possibility to close it, if I do a re-click at the same package.

    Otherwise I find your Package Manager really excellent. Great work!

    • I don’t believe there is any PolicyKit setting that means that you don’t have to enter any passwords. If you set the Muon install and update policy to not needing a password, it will respect it. At any rate, any issue would be with the Qt PolicyKit libraries, as Muon does very little but check with it to see if it has permission.

      A hide mechanism for the details tab may come in later, but in the meantime you can use the splitter separating the package view from the details widget and pulling it down.

  11. blade says:

    I could not compile it in a squeeze, because the library libdebconf-kde isn’t aviable for Debian…

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: