Who needs shape tool when we have text tool

    • neclimdul@lemmy.world
      link
      fedilink
      arrow-up
      35
      ·
      2 months ago

      It does! And it’s so easy to use.

      • Draw a circle with the ellipse selection tool
      • From the edit menu choose “stroke selection” and follow the dialogs
      • Remove your selection

      It’s so obvious I can’t imagine why anyone would be confused.

      • cally [he/they]@pawb.social
        link
        fedilink
        English
        arrow-up
        15
        ·
        2 months ago

        Draw a circle with the ellipse selection tool

        So it does have what is effectively a circle shape tool. I don’t know why people are saying it doesn’t.

        • neclimdul@lemmy.world
          link
          fedilink
          arrow-up
          21
          ·
          2 months ago

          I was being sarcastic because really it doesn’t have a tool with explicit features, just a workaround using a couple features together.

          For a new user it’s very difficult to do a pretty basic task.

        • nasi_goreng@lemmy.zip
          link
          fedilink
          arrow-up
          11
          ·
          2 months ago

          That’s not actual shape tool.

          Shape created by shape tools should be always editable. Using ellipse selection tool means the circle is rasterized.

          • renzev@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            2 months ago

            Paths in Gimp are persistent, non-rasterized, and editable. Just make a circle with the ellipse tool and then convert it to a path.

            • nasi_goreng@lemmy.zip
              link
              fedilink
              arrow-up
              1
              ·
              edit-2
              2 months ago

              That’s still not as intuitive as actual shape tools on any other software.

              If average casual user get confused to it, then it’s a bad UX.

              • renzev@lemmy.world
                link
                fedilink
                arrow-up
                2
                ·
                2 months ago

                Trying to cater to some mythical “average casual user” and avoiding some vague concept of “bad UX” at all cost is how you get unusable garbage like Gnome and Teams.

                • nasi_goreng@lemmy.zip
                  link
                  fedilink
                  arrow-up
                  4
                  ·
                  2 months ago

                  I’m not saying it has to be GNOME or Teams. Gnome is too limiting (I also don’t like it), while Teams is… whatever.

                  It’s just have to be great for advance user, while easy to user for first-time user.

                  Let me give you some example of bad UX, that fixed in other software:

                  • Gradient effect is not editable once you deselect it, you have to recreate it from scratch (you can edit it on Photoshop or Affinity Photo)
                  • There’s should be option to adjust font size with resizing text box instead of trying to input every single number (it’s possible on every major software)
                  • Drawing outside the layer does not retain its information (CSP retains the information)
                  • NDE effects cannot be drag and drop between layer for faster editing
                  • Rotating text cannot be edited (just saw the dev talk about it on Discord)

                  Almost all of the UX problems here are recognized by the dev, even actively discussed on how to fix them!

                  You can make advance application while still catering towards newbies! For example: Clip Studio Paint. They have multiple layout and UI for different use case and audience.

      • rtxn@lemmy.worldM
        link
        fedilink
        arrow-up
        19
        ·
        2 months ago
        1. Because it’s a photo editing tool, not a painter. Different priorities.
        2. Because a shape tool requires non-destructive vector layers.
        3. …and implementing that would require a fundamental overhaul of the current vector backend from 2006.

        The development of 3.0 was focused on GEGL and non-destructive editing. Working on the shape tool in parallel would’ve taken away resources and pushed back the release date even further.