Comments (3)
I tend to agree. For many applications, e.g., linuxdeploy, appimagetool, all linuxdeploy plugins, appimagecraft etc. a desktop file is not needed at all. Those are also the kinds of applications you would not put into a software store or anything, where the desktop file information would be processed.
from type3-runtime.
Within the AppImage ecosystem, we are using desktop files for various tasks, including determining the name of the AppImage, storing a description string of what the application/CLI tool does, and for displaying metadata in App Centers. I don't see why it is a problem to create a desktop file for CLI tools.
Also, not having an icon is not something every AppImage-using tool should need to be able to handle, it only makes the code more complex. By the way, Go does have an icon and this is how my Go AppImage looks:
As per the AppImage specification, an AppImage
MUST contain a .DirIcon file as per the AppDir specification which SHOULD be a 256x256 PNG file.
So this is even coming from the AppDir specification which we have inherited from ROX.
Those are also the kinds of applications you would not put into a software store or anything, where the desktop file information would be processed.
Why would you not put those into App Centers?
from type3-runtime.
I don't see why it is a problem to create a desktop file for CLI tools.
Because you end up having to fill something up that is of no practical to use (except to the appimage ecosystem itself). It's basically being created purely to please the runtime.
As per the AppImage specification
Certainly. The discussion here is about potentially changing the specification, since we're at a point where there is an opportunity to do that.
Within the AppImage ecosystem, we are using desktop files for various tasks, including determining the name of the AppImage, storing a description string of what the application/CLI tool does, and for displaying metadata in App Centers.
I think appimage-specific metadata should live in the appimage header, rather than be tacked-on to a different specification that is intended for something else.
Worse case scenario I'll just go my own way without having compatibility with appimages (besides the basic user UX), but I do think there's value in cooperating instead.
from type3-runtime.
Related Issues (13)
- Brainstorming about the design goals of a type-3 image format HOT 20
- Multi-Layer AppImages HOT 9
- Versioning AppImage components HOT 1
- remove limitation on number of applications HOT 4
- Clarify Image format, runtime, header HOT 3
- ELF resources HOT 14
- Is it technically possible to make an AppImage that is also a valid zip file? HOT 18
- FUSE compatibility HOT 1
- Proper sandboxing HOT 1
- Reason for supporting different image formats HOT 3
- Desktop Integration Data without accessing payload HOT 9
- Consider shell scripting as language
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from type3-runtime.