<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jan 15, 2014 at 4:33 PM, Harald Sitter <span dir="ltr"><<a href="mailto:apachelogger@ubuntu.com" target="_blank">apachelogger@ubuntu.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5">On Wed, Jan 15, 2014 at 3:54 PM, Achim Bohnet <<a href="mailto:allee@kubuntu.org">allee@kubuntu.org</a>> wrote:<br>
> On Mittwoch 08 Jan 2014 16:28:07 Aleix Pol wrote:<br>
>> On Wed, Jan 8, 2014 at 4:20 PM, Harald Sitter<br>
> <<a href="mailto:apachelogger@ubuntu.com">apachelogger@ubuntu.com</a>>wrote:<br>
>> > On Wed, Jan 8, 2014 at 2:42 PM, Aleix Pol <<a href="mailto:aleixpol@kde.org">aleixpol@kde.org</a>> wrote:<br>
>> > > On Wed, Jan 8, 2014 at 1:03 PM, Jonathan Riddell <<a href="mailto:jr@jriddell.org">jr@jriddell.org</a>><br>
>> ><br>
>> > wrote:<br>
>> > >> On Tue, Jan 07, 2014 at 02:25:27PM -0800, Scarlett Clark wrote:<br>
>> > >> > Is this the default package manager? Or Muon?<br>
>> > >> ><br>
>> > >> > I need all ways to bring this up eg.. command line. I have so far<br>
>> ><br>
>> > in<br>
>> ><br>
>> > >> > a<br>
>> > >> ><br>
>> > >> > search from KickOff and KickOff->Programs->Muon Discover<br>
>> > >><br>
>> > >> We have both Muon and Muon Discover installed by default. Arguably<br>
>> > >> this<br>
>> > >> is application duplication and very un-ubuntu.<br>
>> > >><br>
>> > >> Does anyone have an opinion of whether Muon Discover is mature enough<br>
>> > >> to<br>
>> > >> stand along and for Muon to be removed from the images?<br>
>> > >><br>
>> > >> You can access it by KickOff -> Computer -> Software Centre too which<br>
>> ><br>
>> > I'd<br>
>> ><br>
>> > >> expect to be the primary method.<br>
>> > >><br>
>> > >> Jonathan<br>
>> > >><br>
>> > >> --<br>
>> > >> kubuntu-devel mailing list<br>
>> > >> <a href="mailto:kubuntu-devel@lists.ubuntu.com">kubuntu-devel@lists.ubuntu.com</a><br>
>> > >> Modify settings or unsubscribe at:<br>
>> > >> <a href="https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel</a><br>
>> > ><br>
>> > > I would say that the decision is not really about maturity but about<br>
>> > > user<br>
>> > > target. I don't think an end-user should understand all the semantics<br>
>> ><br>
>> > that<br>
>> ><br>
>> > > Muon Package Manager exposes. If a user has the knowledge to use Muon PM<br>
>> ><br>
>> > he<br>
>> ><br>
>> > > has the knowledge to install it from Discover or even apt-get.<br>
>> ><br>
>> > Indeed. The argument never was that software center or discover<br>
>> > weren't mature enough, but that they do not deal in packages. They<br>
>> > deal in applications (read: in things that have a desktop file). So if<br>
>> > you want or need to install a package (say 'bzip2') you won't be able<br>
>> > to do that with discover because of the way it is designed.<br>
>> ><br>
>> > Personally I always found this argument silly because it implies that<br>
>> > a user knows the difference between Muon and Muon Discover and will<br>
>> > choose the correct tool for the job at hand <- so very very very<br>
>> > unlikely...<br>
>> ><br>
>> > Really there are three groups of people we have to consider:<br>
>> > a) the user who only wants to installation an application and will not<br>
>> > ever want to install a package (by himself, support cases excluded<br>
>> > becasue those usually will offer concrete apt-get commands anyway)<br>
>> > b) the user who perhaps could be called a sysadmin and wants to<br>
>> > explicitly manage packages, but likes to do it in a GUI<br>
>> > c) the user who likes direct control but feels that a GUI slows him down<br>
>> ><br>
>> > And here is the thing.<br>
>> > A user of group a) won't be able to graps the concept of either b) or<br>
>> > c) and have a very hard time trying to manage 'apps'.<br>
>> > A user of group b) will be able to deal with the usage paradigm of a)<br>
>> > but might not be able to do what c) does.<br>
>> > A user of group c) will be able to do manage 'apps' and 'packages' given a<br>
>> > gui.<br>
>> ><br>
>> > Looking at the presented use cases there is no reason why muon (the<br>
>> > package manager) needs to be part of the default install. You could<br>
>> > technically even remove apt-get itself. Because b) will be able to use<br>
>> > muon-discover to install muon and c) will be able to use muon-discover<br>
>> > to install muon to install apt-get. Of course latter is not very<br>
>> > convenient so one can make an argument for keeping apt-get regardless<br>
>> > (plus I doubt you could remove it anyway ;))<br>
>> ><br>
>> > Long story short: if someone wants a gui package manger, they can<br>
>> > manually install muon via discover or apt-get, absolutely no reason<br>
>> > why we'd need it in the default install.<br>
>> ><br>
>> > HS<br>
>> ><br>
>> > --<br>
>> > kubuntu-devel mailing list<br>
>> > <a href="mailto:kubuntu-devel@lists.ubuntu.com">kubuntu-devel@lists.ubuntu.com</a><br>
>> > Modify settings or unsubscribe at:<br>
>> > <a href="https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel</a><br>
>><br>
>> FWIW, bzip should probably be installable from Discover, since it's an<br>
>> end-user application.<br>
>> What the user won't be able to find in discover is libbz2. Arguably, -dev<br>
>> packages should be available in discover as well.<br>
><br>
> FWIW I would disagree here. People using the command line with bzip or<br>
> compiler&co, using -dev pkgs, can be expected to use muon or apt-get.<br>
> (let's call muon the export-mode of muon-discover ;-) Start muon and exit<br>
> muon-discover when the tobe-done 'Export Mode' button is pressed ;-) )<br>
><br>
> On the other hand: try to search for android or kdeconnect or 'network<br>
> management' in muon-discover: it finds nothing, but that's wrong IMHO. The<br>
> target group of muon-discover doesn't know if it's a plasma/kded plugin or a<br>
> application (aka binary in /usr/...bin with desktop file).<br>
><br>
> IMHO as it is, muon-discover misses an important group of 'looks-like-an-<br>
> application' that's important for newbies, so there is still a need for muon.<br>
<br>
</div></div>I absolutely agree.<br>
This is however a two folded issue actually.<br>
<br>
There is those things that expand a thing, but on their own they do<br>
not make sense/may not be an application. This includes for example<br>
amarok's moodbar plugin, if you navigate to amarok and select the<br>
addons tab you'll get it listed there. If you however simply search<br>
for moodbar nothing shows up. It is not an application, but it is an<br>
addon feature that a person should be able to search for, however the<br>
result ought not be an own page, but instead take you to Amarok's<br>
addon page.<br>
<br>
And then there is the things you mentioned. Things that on a technical<br>
level are addons/plugins to the actual application but ought to be<br>
searchable on their own.<br>
This includes just about everything that has a desktop file in<br>
usr/share/kde4/services (minus a whole bunch of other stuff ;))...<br>
incomplete list:<br>
plasma applets<br>
plasma wallpapers (?)<br>
plasma runners<br>
plasma themes<br>
KCMs<br>
kipi-plugins<br>
<br>
To express those groups more clearly: there are addons that expand<br>
*one* application and there are addons that expand *multiple*<br>
applications. Plasma* can be used in either<br>
plasma-desktop/plasma-netbook/plasma-active. KCMs can be used in<br>
systemsettings/kinfocenter/applications. And so on.<br>
<br>
The former of the two has no visual identity, they provide abilities<br>
to the application. Latter has a visual identity and supply additional<br>
features within an application.<br>
<br>
Now why would one search result lead to the application's addon and<br>
the other not? For one, because one group can have multiple<br>
applications they add on to, so that would look silly; and for another<br>
KCMs for example make sense on their own. As an application. The<br>
example I hit the other day was the colord kcm. If you search for<br>
color correction in discover you get nooothing. Now people might argue<br>
that it should list colord, and I agree with that. colord is the means<br>
for the technical part of color correction. The KCM is the actual user<br>
facing frontend for it.<br>
<br>
Since I started rambling somewhere half way through the mail I am<br>
going to stop now :P<br>
<div class=""><div class="h5"><br>
HS<br>
<br>
--<br>
kubuntu-devel mailing list<br>
<a href="mailto:kubuntu-devel@lists.ubuntu.com">kubuntu-devel@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel</a><br>
</div></div></blockquote></div><br></div><div class="gmail_extra">Actually, improving the visibility of Addons is indeed very interesting. I would suggest you to take a look at the "reviewsOnOverview" branch in muon, where you'll find a redesigned version of the application page. Maybe we can push it for 2.2, last time I played with it was ready but I didn't merge it for lack of feedback (and being busy with different issues, of course).</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Also we could use addons names as a search parameter, if you think it's appropriate.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Aleix</div>
</div>