It’s not done yet, but I figured I’d show off a little bit since I have been using this for a few weeks now. This is the “swirl”. It’s heavily inspired by the helix with some notable changes:

  • mbk Choc Spacing (Dimensions are about 12.5cm x 8.5cm on either half)
  • Reversible roller encoders on the top inner switch

https://github.com/vmorganp/swirl

  • 𝕸𝖔𝖘𝖘@infosec.pub
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Looks awesome! Why use two boards and the trrs cable? Couldn’t you use one board and the cable? Or can each of the two halves be used independently of one another?

    • KeyboardGoesBrrr@lemmy.worldOP
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago

      I have a larger build and nailing down the ergonomics is really hard without a split board.

      I could use a unibody split but this is just easier to adjust and travel with this way.

      I could also use either half independently. (with a quick firmware change on the right, but still)

    • dnzm@kbin.social
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      Because this allows you to keep the halves further apart, which is considered more ergonomical.

      Typically, each half can, in fact, be used independently (they each have their own microcontroller).

        • dnzm@kbin.social
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Because then things like holding shift on one half and a letter on the other wouldn’t work.

          • Num10ck@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            if those issues could be solved by software drivers would the cord free aesthetic be preferred?

            • KeyboardGoesBrrr@lemmy.worldOP
              link
              fedilink
              arrow-up
              3
              ·
              1 year ago

              In a perfect world, yeah totally. I could use controllers that are approximately twice the price (nice!nanos) and have to rewrite the firmware (qmk -> zmk) and deal with Bluetooth, or I could just use wires and have it “just work™”. I personally prefer this, but tons of people go the wireless route.