I’m working on a project that needs lots of toolbars on screen at once, even though not all of them will be used at the same time. So, I’m modelling this ‘foldable’ dock widget after what I remember Photoshop panels used to be like.

It’s a work in progress, but would like to hear constructive suggestions.

https://blocks.programming.dev/0101100101/42c5d67f86c049baa3500aa38e439f8a

  • 0101100101OP
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 days ago

    In the case of this gist, it’s premature optimization. Generally it’s necessary cuz new implementations come along often.

    That sounds terribly inexperienced. That’s exactly what updates to code are for. You cannot manage all kind of, sort of similar but different libraries with one code base. It would be horrific to even consider it.

    • logging_strict
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      edit-2
      4 days ago

      The same argument can be made for supporting Windows and MacOS. Don’t have these dev environments. But somehow found a way to support these platforms.

      If you look into it, pyQt[x] and pySide[x] aren’t all that different. The intent of PySide is to keep them for the most part compatible.

      Don’t have to manage everything, just what is being used.

      Doing the wrong thing explains most my packages:

      wreck – dependency management

      drain-swamp with drain-swamp-action – build backend with build plugins

      logging-strict – strictly validated logging configuration

      pytest-logging-strict – the same thing except a pytest plugin

      What else am i not supposed to do?