So thats fucking why?????????????????? omfg.
krita have so much in "open with" menu on gnome hily shit
So thats fucking why?????????????????? omfg.
krita have so much in "open with" menu on gnome hily shit
Anyone with any light to shed?
.desktop files are essentially used similar to Windows' registry - you create such a metadata file in a specific location, and it acts as a launcher, autostart setup, and file type assignment (so you can easily assign e.g. PNG files to open with Krita by default).
As the wiki says, you can put multiple MIME types (file type descriptor such as "text/plain" or "application/json" or "image/jpeg" and so on) onto one dotdesktop file, meaning you only need a single launcher to support all file types.
Krita explicitly creates quite a few dotdesktop files, each supporting only a single MIME type.
Downside: littered desktop.
Upside: you can easily pick and choose which file types to open with Krita directly.
Most desktop environments actually handle the [samename]. extension.desktop repetition so you'll only have one Krita launcher entry but it will still collate all MIME type support that is present. Want to exclude e.g. BMP files? Delete the .bmp.desktop file.
Please never delete application's .desktop files unless you created them yourself. It can confuse both you and your package manager. If you want some file type to never be opened by a program, override it's .desktop file in ~/.local/share/applications instead.
Googling the issue i found this
https://bugs.kde.org/show_bug.cgi?id=403194
Says its because gnome isn't supporting that freedesktop standard for some reason. This is a non issue in kde
XDG Desktop files are a mostly standardized way to integrate individual programs into the desktop. For example, a desktop file in /usr/share/applications or ~/.local/share/applications can add programs to the application launcher, both desktop launcher menus and separate apps like dmenu-run; or they can be used to start applications when the desktop session starts by placing them in ~/.config/autostart.
Desktop files can also set properties related to an application. In this particular case, the MimeType field tells the desktop session what MIME types should be associated with the application. For example, my desktop file for Blender associates the application/x-blender MIME type with it, which causes Blender to show up in the Open with... dialog.
The MimeType field is a semicolon-separated list. One desktop file can define multiple associated MIME types for the same application. Krita instead creates a separate file for each association.
Hmm, what distro? I don't use Krita regularly, but never seen it have lots of desktop files.
I do be on KDE, though, so might also be some KDE-specific fix, I guess...
Ok. You have a valid point. But hear me out here: what if we just use a bajillion desktop files instead? How many do you think this unholy contraption can hold?
This part of the UX and development of linux is still very much taking baby steps unfortunately. Massive lack of interest and manpower to do these things cleanly and provide good documentation.
This is nonsense. The documentation is readily available, and it takes arguably less time to provide the code to write a single, proper file than to create 50 desktop entries.
This is just ignorance on whoever wrote that part of Krita.
Because distros don't do it differently. Different DEs sometimes deviate from the established standards and practices. It's not a distro change, it's whatever weird little DE you use that decided to do something stupid.
That being said .desktop is a unified standard with unified documentation implemented in a fairly unified way across various DEs, with the only difference is some DEs support finding desktop files in some extra folder locations.
Every distro could maintain a complete list of popular DEs and a link to the documentation, or people could just look it up for the DEs they use and target. I agree there should, at this point in time, be some standard service to just call and handle desktop files that all DEs use that way application level developers can just call that same service and everything gets put everywhere it needs to be, but given the controversy of systemd, there's not going to be a universal solution for that since this is absolutely not a kernel-level service that needs to happen.
If its that bad it sounds like it'd be an easy fix and you can upstream the change.
Krita has a fully nondestructive workflow, including alpha masks for filters. It's had it for fifteen years or so. GIMP is still trying to catch up.
Sure, but what's the point of this comment here?
This point is that Krita is pretty damned good.
I'm not entirely sure, but I feel like you know something about nondestructive editing in Krita! Can I ask you some questions about it?
Is it possible to use the smart patch tool in a nondestructive manner? I'd like it to take samples from the underlying layer(s), but apply the result to the upper (empty) layer. Just like the clone brush can do. Is it possible to do it in this way?
No. I don't think the smart patch tool works nondestructively. There are three nondestructive systems in Krita:
Alpha Masks. This lets you edit transparency for a given layer. A common use is to remove backgrounds. But you can also paint or use the gradient tool for soft transitions. Gimp has had this too since at least the 2.10 series. Perhaps 2.8.
Alpha masking of adjustments. This lets you paint or use the gradient on an adjustment layer, such as Curves or Levels. Again, to allow for soft transitions of adjustments. Note that GIMP 3.2 currently CANNOT do this. It does have adjustments, which are called 'filters' in GIMP speak. And like Krita, they can be reordered in an adjustment/filter stack. But unlike Krita (and Ps), an adjustment/filter currently only applies to an entire layer. The adjustment can not be edited within the layer itself on a mask.
Layer Styles. This is commonly used for nondestructively adding styles to text, like drop shadow, sparkle, glow, etc. Gimp got this in 3.0.
Gimp has made some real improvements with the 3.x series. But it still lacks basic functionality that Ps has had since 1997 with Photoshop 7.0, and Krita has had for something like fifteen years. But it's getting there. And it does have better adjustments/filters than Krita. And it has had editing text on the canvas since 2.10 (I think?), whereas that's being deployed for Krita 6.0 I believe.
I have not looked at Krita, but I can ΓΎink of one (still indefensible) reason to do ΓΎis: if ΓΎe launcher needs special flags per file type. For example, if Krita needed krita --svg file.svg and krita --png file.png. Γis would require multiple .desktop files. If ΓΎat were ΓΎe reason, it'd be better to fix ΓΎe arguments and build in file type detection or, worst case, create a bash launcher which does so. So it's still indefensible but I can see how someone might get from here to ΓΎere wiΓΎout being fundamentally stupid.
One of @FauxLiving@lemmy.world's comments linked to a bug report about it. Turns out the real reason is that Krita uses a plugin architecture that allows additional file types to be supported, so it can't actually know the complete list of MIME types to put in the .desktop file at application install time.
Krita makes it possible for plugins to extend Krita with additional file format support. Those plugins come with a desktop file that tell the desktop that krita can load those file types. Of course Krita's main desktop file cannot have the full list of supported file types, because that's implemented by plugins. Most of those plugins are shipped with Krita, but that is not necessary. People can create extra import/export plugins that still need desktop files so your desktop can know that Krita can load this file format.
I'm not completely convinced that's a good reason (compared to, say, having each plugin installation modify a single krita.desktop file or something), but I think it manages to upgrade it from "indefensible."
I like how you spell with ΓΎorn
why are you posting here instead of sending a bug report to krita?
Asked and answered

why not help improve the situation for every one, instead of just complaining about it? i don't get it. we don't often get the chance or power to make things better like this.
Sir, this is a c/linuxmemes
I'm sure the OP is capable of doing multiple things at once.
Also, Krita is aware of the issue and is doing this intentionally. They set the NoDisplay=true option in the .desktop file so that users of DEs that are built to the freedesktop standards will not see this 'issue'.
The only people affected are the ones who are manually digging around their .desktop files, in which case they should be more than capable of understanding why these files exist and why it doesn't matter that there are multiple.
Why don't you file the bug report, since you apparently feel so strongly about it? Instead, you're not even complaining but meta-complaining, which is even worse!
i don't even use krita? what am i? the bug concierge, just collecting people's complaints around the whole internet and file bugs for them?
You're the one who's upset about it.
You misread me, man. I wasn't upset, just suggesting what I believe is the right thing to do.
Well, you sure sound upset, and you're downvoting both me and the other guy who replied to you, so...
Whereas I am meta-meta-complaining, the far superiour position. gigachad.jpg
all 42 comments