AppImages are not "installed" #133
Comments
|
I'm sorry, but I disagree here. I get it, "technically" you are right. "Applications", to me, sounds too generic. We should difference appimages that you have casually lying around the Downloads folder, to the ones that show up in the system menu. I actually spent some time while developing Gear Lever to decide the proper labels for "Installed applications" and the "Integrate" button the comes out when you open a new file. The goal here was to make an app that was easy to use and with familiar controls for most users. |
|
Well, AppImages are a form of application bundles, and people always want to treat it as if they were "packages" because a) they are used to packages and b) most desktop environments lack proper native support for application bundles. Proper application bundle support in desktop environments is the thing that should be improved, imho. |
|
How about saying "Integrating..." instead of "Installing..."? |
Since we are just changing a string, but a very important one, is it worth the time of all the translators who worked on the project? Not in my option, I'm sorry |
|
"Integrating..."
It is very important for me. The reason for AppImages to exist is so that software doesn't need to be installed. Saying AppImages are "installed" is like saying an electric car is "fueled". The whole point of an electric car is that it doesn't need any fuel. |
gearlever/src/InstalledAppsList.py
Line 55 in 3702f37
AppImages are not "installed", and that is the main point. You download them, make them executable, done. There is nothing to "install". In fact, I specifically designed the file format so that applications would no longer need to be installed.
Hence, I suggest to just say "Applications" there, and not use the word "installed". Thanks for your consideration!
The text was updated successfully, but these errors were encountered: