• @[email protected]
    link
    fedilink
    English
    233 days ago

    I’m not sure, but that’s exciting if so

    GIMP UI as is hasn’t changed much in 20 years.

    • @TexasDrunk
      link
      English
      83 days ago

      I remember GIMPshop being a thing back in the day. It was much easier for me, but it was abandoned ages ago. PhotoGIMP is fine, but it’s missing a lot of the QoL stuff that makes Photoshop better.

      • @[email protected]
        link
        fedilink
        English
        173 days ago

        Yeah

        And that’s not to say GIMP is bad software, it’s competing with a design app that’s almost a monopoly worth billions of dollars. That’s a high bar to beat for free.

        • @TexasDrunk
          link
          English
          43 days ago

          Oh, no kidding! I have nothing but love for it. I’m just over here musing about it. The fact that it can do so much and get that close is damned amazing.

    • @Valmond
      link
      English
      13 days ago

      And their invented forced onto you file system 🤢you can’t open a jpg, change sonething and then you jhave to dance around the export, nit save when clising etc etc. Why devs, why?

      Would be super cool if they got things up just a bit.

      • @[email protected]
        link
        fedilink
        English
        1
        edit-2
        2 days ago

        Why devs, why?

        When you’re opening a jpeg it is transformed into a Gimp datafile so you can edit it.
        “Saving” as jpeg would remove all your editing history, collapse all layers, and perform lossy compression on the resulting image.
        Since losing most of the info included in your open file is not really what you want when you hit “save”, they put it behind the “Export” button.

        I guess it would be more logically consistent if the workflow for editing images was to create a new Gimp project, then import a jpeg into it, the way some video editing software does it.
        But that would be even less convenient.

        • @Valmond
          link
          English
          22 days ago

          Yeah I know, I just don’t want to save that clutter in a file format you can’t use elsewhere.

          Photoshop only makes you save in the .psd format if you have added layers, data outside the image etc. Otherwise it just saves it to a jpg or png or whatever it was when you opened it. This is the correct way IMO.

        • macniel
          link
          fedilink
          English
          2
          edit-2
          3 days ago

          They are complaining that Gimp only allows to save in reconstructable formats (e.g. xcf) even when you opened baked fileformats (in this case jpeg)

          In Gimp you have to export to those file formats as you would lose layer and history data as they don’t support that.

          • @[email protected]
            link
            fedilink
            English
            13 days ago

            ah, yes, saving and exporting used to be conflated. That shouldn’t be a problem, just hit export instead of save

            • @Valmond
              link
              English
              13 days ago

              Yeah and then when you close the image it says it hasn’t been saved, which is both annoying and error prone.

              Not a super big deal you’d say but when you resize lots of images it is, for example. Especially as it worked differently and one day they forced this bad UX choice.

      • @[email protected]
        link
        fedilink
        English
        33 days ago

        I see how that’s useful for workflows…

        I have the same complaint with Affinity Photo when I make Star Trek memes and now have a bunch of .afphoto project files, when I’m often just adding text to a jpeg.