Apply instead of install and uninstall in package installer

[fadi]

Why mx package installer is not using apply instead of the two buttons, install and uninstall? the current method means I can install and uninstall packages in separate transactions . I believe it is too late to change it to the synaptic like method, isn't it?

[j2mcgreg]

Why mx package installer is not using apply instead of the two buttons, install and uninstall? the current method means I can install and uninstall packages in separate transactions . I believe it is too late to change it to the synaptic like method, isn't it?

They all have the same function IE Do This
If you want to use Synaptic instead, do so. Like MXPI or Discover in KDE, it's just a GUI for apt.

[Eadwine Rose]

I believe you can use the install button to install OVER what is already installed.

So.. replacing it with apply means the program doesn't know if you want to reinstall, or uninstall.

[dolphin_oracle]

Why mx package installer is not using apply instead of the two buttons, install and uninstall? the current method means I can install and uninstall packages in separate transactions . I believe it is too late to change it to the synaptic like method, isn't it?

Thanks for the question.

As you've probably noticed, the buttons change on function. there are two, and if you select a previously installed package, both buttons are enabled and change to "uninstall" or "reinstall". the only button enabled otherwise is install.

we only have one box mark function, on or off. synaptic has many. could our setup be different, maybe, but that's the solution we have and its worked out pretty well so far.

[Adrian]

I designed it like that because I found the Synaptic way potentially confusing to user, "Apply" what? Also, you'd need to right-click or have another way to select what you want to do with the package.

Just for history sake this tool was not meant to replace Synaptic (that's why we still package it) it was supposed to be an easy way to install some packages, now listed under Popular apps, in a simple way, it didn't even have the option to remove packages and all the other tabs didn't exist -- that's why is called "mx-packageinstaller" and not "mx-packagemanager" or something like that. The GUI was inspired by, some might say copied from, an old GTK program "metapackage-installer" (or meta-installer, don't remember exactly) but since I don't do GTK the entire code is written by me and has absolutely no link to that tool.

Some copied my tool and put it in an arch derived distro without any credit and removing the copyright note... but that's fine, it's better than to blame for the bugs introduced by other people.

[dolphin_oracle]

Some copied my tool and put it in an arch derived distro without any credit and removing the copyright note... but that's fine, it's better than to blame for the bugs introduced by other people.

[fadi]

I designed it like that because I found the Synaptic way potentially confusing to user, "Apply" what? Also, you'd need to right-click or have another way to select what you want to do with the package.

I hope you change your mind in the years to come . The synaptic method is actually more intuitive, and MXPI is now bigger than what it was intended to .

[Eadwine Rose]

It is in the eye of the beholder. You like Synaptic better, then please use that.

For me, combo. New installs are being done using MXPI because that tool does it better in some situations. I am sure some people can name a few.

[j2mcgreg]

It is in the eye of the beholder. You like Synaptic better, then please use that.

For me, combo. New installs are being done using MXPI because that tool does it better in some situations. I am sure some people can name a few.

I agree. I use them interchangeably as well.

[Stevo]

I designed it like that because I found the Synaptic way potentially confusing to user, "Apply" what? Also, you'd need to right-click or have another way to select what you want to do with the package.

I hope you change your mind in the years to come . The synaptic method is actually more intuitive, and MXPI is now bigger than what it was intended to .

It's open source; and you're free to fork it.