-
-
Notifications
You must be signed in to change notification settings - Fork 565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some troubles with specification #955
Comments
Hi @Anyeos and welcome to AppImage. Thanks for sharing your thoughts. This sort of feedback is very valuable to us.
An icon is mandatory as per the AppImage specification:
The Unfortunately, some desktops cannot use this to render the icon into the menus, so if you want that, you also need icon files below
Given your comment, I will change this to SHOULD in the spec. We have been recommending it to our uses anyway, and our tools have been doing it since a long time.
As per the spec, it is not strictly required, but in practice most AppImages do contain it:
Err, it exists. This is how it looks with But there is currently a bug AppImageCommunity/libappimage#103 that prevents thumbails from being generated properly. There is also a GNOME thumbnailer and a KDE thumbnailer, but
thumbnailers need to be installed in the system, too - unless they are pre-installed by distributions by default. (Distributions are pushing their own formats like Snappy and Flatpak thoguh.)
Desktop integration is entirely optional. You don't need it. You can run an AppImage like this: |
Yes, you're right but I point from the perspective of practical use. I mean, thumb is something that will help. But when I was talking about AppImageLauncher I am comparing the simplicity of directly copy and run an AppImage. Something that is not very hard to learn for someone. Versus a more sofisticated thing like AppImageLauncher but if somebody wants to use it, there is. It is a great new that there already exists a thumbnailer. But sad to ear that it is not working because there are a bug. Anyway, somebody will fix it some day, I hope. I don't want more from AppImage, because it already do the right work. But I just wanted to tell some points to not forget the practical perspective. So, what we need now is making work the thumbnailer and a matter to include the icon on the menus. But I think that the menu thing (the whole .desktop thing as freedesktop specs) got out of the AppImage purpose. Because I think it is ok to not having a menu icon, because the menu must be created by some installer and not by the Application itself. But that is my opinion. |
Should be fixed in AppImageCommunity/appimaged#78. |
Sorry guys but it is some confusing and time consuming for me being so "free" in the specifications.
I suggest a review with more practical cases.
Because in my case I need to maintain six machines. And with five different flavours (different person):
The real case is when I need to update all that systems to get updated apps. The problem is that I need to do a lot of work just only installing an AppImage because:
The solution can be to make including an icon a requisite.
We can develop something like (exe-thumbnailer) so Nautilus and likewise can show the real app icon extracted from the AppImage.
Why I think that. Because if my sister, my mother, my father,... need to install something. It will be more easy if it is more like a Windows exe showing an icon (that helps a lot identifying a software). So, they will don't need me to update the apps.
And, if I must install something like AppImageLauncher... Where is the point of having an AppImage? The only advantage is more projects are packaging the software in AppImage format. So I can get an updated binary easily but installing something like AppImageLauncher add some uneeded complexity.
So, as I said above, the solution can be impose the use of an icon and make an "appimage-thumbnailer" plugin for file managers like Nautilus.
I hope you understand me. I don't want to impose nothing. I just want to present my real case of use.
The text was updated successfully, but these errors were encountered: