• Paranoid Factoid@lemmy.world
    3·
    24 minutes ago

    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.

  • realitaetsverlust@piefed.zipEnglish
    51·
    2 hours ago

    I know this is a meme, but in case it’s has a serious undertone, the question in this case is - who really cares?

    Those are desktop files. You usually don’t manually look into that folder in the terminal. It’s not like a snap where your lsblk output is being cluttered.

    This is such a minor problem that it’s barely worth being talked about. It’s a mere “best practice was ignored” case that has Z E R O impact on performance, maintainability or usability.

    • ILikeBoobies@lemmy.ca
      2·
      17 minutes ago

      My application menu did get cluttered with multiple krita entries.

      Which was a minor annoyance.

    • liinux@pawb.social
      2·
      34 minutes ago

      I’m not sure about this case because I don’t use flatpak that much, but to be honest I hate when I install an Electron based program such Freetube, and even though I installed the BIN binary (arch btw, not happened this on Debian based distros) for some reason my package manager decided to install the whole Electron framework with DE included. I get that it depends on it to work, but I don’t need 40 Electron packages to show in my Wofi that I would never use, is so ugly. The same with Qt programs and any single KDE app (but I understand in this case)

      I mean, yeah I understand that Freetube depend on Electron to work, but why when installing Steam this is not the case?

      • realitaetsverlust@piefed.zipEnglish
        2·
        3 minutes ago

        but why when installing Steam this is not the case?

        Because steam has no application-dependencies, it bundles everything into one binary, including the electron binary, and ships everything in one go. However, steam still has system-dependencies that have to be installed and will pop up in rofi.

      • realitaetsverlust@piefed.zipEnglish
        1·
        2 minutes ago

        I don’t know if you’re ragebaiting or are just a massive fucking asshole tbh, but when someone develops an application for free and for fun for anyone to use, I’m not complaining about too many fucking .desktop files.

  • sepi@piefed.socialEnglish
    1·
    1 hour ago

    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?

  • Ephera@lemmy.mlEnglish
    8·
    6 hours ago

    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…

    • fonix232@fedia.io
      42·
      8 hours ago

      .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.

    • rtxn@lemmy.worldM
      11·
      8 hours ago

      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.

  • it_depends_man@lemmy.worldBanned from community
    133·
    8 hours ago

    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.

    • scrion@lemmy.world
      261·
      7 hours ago

      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.

        • vagrancyand@sh.itjust.worksEnglish
          10·
          6 hours ago

          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.

  • Ŝan • 𐑖ƨɤ@piefed.zipEnglish
    910·
    4 hours ago

    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.

    • grue@lemmy.world
      3·
      1 hour ago

      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.”

      • nialv7@lemmy.world
        11·
        3 hours ago

        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.

        • FauxLiving@lemmy.world
          41·
          2 hours ago

          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.

        • grue@lemmy.world
          31·
          2 hours ago

          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!

          • nialv7@lemmy.world
            1·
            1 hour ago

            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?