Live data from Hacker News

Show HN: Bayleaf – Building a low-profile wireless split keyboard

graz.io

241–250 of 259 posts

Re: Show HN: Bayleaf – Building a low-profile wireless split keyboard

#241
post #59

Earlier quoted context omitted.

There is always Glove80, choc switches have very little travel.

Eh, Choc switches have less travel than MX switches but I wouldn't say they have very little travel. Chocs main selling point is the form factor which allows the keyboard chassis to be much thinner. MX switches usually have 4mm of travel, Choc switches have 3mm, while the PG1316S switches used in OPs keyboard only have 1.8mm. I think Apples current switches are even shallower at ~1mm.

> while the PG1316S switches used in OPs keyboard only have 1.8mm

Do you happen to know of a resource around this topic? I'd love to know what the actual lowest travel switches are. In my experience it's the Macbook's.

Re: Show HN: Bayleaf – Building a low-profile wireless split keyboard

#242
post #230

Earlier quoted context omitted.

There’s no issue with a computer recognizing two keyboards, but smaller keyboards often lack all the keys found on a standard one. So, you’ll need to use modifiers to create the keystroke and then send it to the computer. If you press a modifier on one half, the other half needs to be aware of it to send the final keystroke. Creating a layout with these modifier-based key combinations is just a small part of the many…

Wouldn't operating system take care of that?

When you have two halves of a keyboard recognized as separate keyboards by the computer, then just like you said. For example, if you press shift on the left half and u on the right, the computer first sees the shift and then the u. It then types a capital U.

But in my case, let's say I don't have any numbers on the keyboard. Instead, I use modifier keys to create a layer for numeric values. So, when I press a modifier on the left, the computer won't notice. Then, pressing what would normally be the U key on the right sends a 7 instead. The computer just sees a 7 being pressed.

Re: Show HN: Bayleaf – Building a low-profile wireless split keyboard

#243
post #201

Earlier quoted context omitted.

Keen eye, initially I did sort the right split from left-to-right. But also over time the fat from the fingers affected the color as well, so I figured it's a loosing battle anyway. I'm waiting for a white colored MJF print, which should eliminate these color woes once I figure out the proper dimensions.

I’m really good at helping pack vehicles for moves. My kid got to take three extra boxes and the driver got use of the rear view mirror back because I repacked the car. So you need some sort of sealant on the keys? Or maybe just a flame polish?

Sealant is not a bad shout once I find the perfect switchcap fit. This elusive tolerance gap has been my moby dick moment for some time. (So when I get around to buy a resin printer)

Re: Show HN: Bayleaf – Building a low-profile wireless split keyboard

#244
post #206
post #42

sgraz beat me to it! I’m working on an almost the same project (thin, slick, aluminium, ortholinear). Guess I’ll have someone to look up to. (:

Keep me posted! Whats your bsky/x?

Oh, believe me I’ll contact you the moment I encounter a hiccup. xD

I use neither. I’m @volemo@mathstodon.xyz.

Re: Show HN: Bayleaf – Building a low-profile wireless split keyboard

#246
Beautiful!

I have these ultra thin bt keyboards that came in a leather ipad case from Restoration Hardware... SUPER THIN.

These bitches better have a lot of magnets! (oh saw that in future. and the LED thingy -- if you can have a display in the side panels, that would be nifty - and a second BT object? Whereby the display in the side panels is BT to phone and thus get distractions.

my problem with small super thin BT keyboards is that the materials are too slippy -- so a tacky-ish finish so they dont slide around when on a surface such as a pant leg or so...

also, a curved version of this would be great for a sleave version - with magnets so that you slap one on your fore-arm. could even have power/connectivity coming from wires in the garment that they attach to.

Magnets basically. Need lots.

--

what if... since the thing is so small, the actual object is the mouse? So you can choose l/r object and then just grab it and mouse about?

Re: Show HN: Bayleaf – Building a low-profile wireless split keyboard

#247
post #245
post #210

Earlier quoted context omitted.

Li-Po 401235

Hmm, 150 mAh? How long does it last for in real use? Do you have to charge the keyboard often?

Yep 150 mAh, it's what I had on hand. But I should have space for 300-500 mAh. I recharge the left (master peripheral) once per ~1.5 weeks. Right side only needs recharging every 2–3 weeks.

Re: Show HN: Bayleaf – Building a low-profile wireless split keyboard

#248
post #247
post #245

Earlier quoted context omitted.

Hmm, 150 mAh? How long does it last for in real use? Do you have to charge the keyboard often?

Yep 150 mAh, it's what I had on hand. But I should have space for 300-500 mAh. I recharge the left (master peripheral) once per ~1.5 weeks. Right side only needs recharging every 2–3 weeks.

I see. Thanks!

Re: Show HN: Bayleaf – Building a low-profile wireless split keyboard

#249

That's really not ergonomic.

Why do you think that? Split keyboards are considerably more ergonomic than regular keyboards.

Compared to a regular, yes, but from the site: "Ergonomics — not gonna lie this is a planned form-over-function kind of deal."

You can see the video. There is no stagger and no tilting and the person is clearly typing at an angle.

Re: Show HN: Bayleaf – Building a low-profile wireless split keyboard

#250
post #242

Earlier quoted context omitted.

Wouldn't operating system take care of that?

When you have two halves of a keyboard recognized as separate keyboards by the computer, then just like you said. For example, if you press shift on the left half and u on the right, the computer first sees the shift and then the u. It then types a capital U. But in my case, let's say I don't have any numbers on the keyboard. Instead, I use modifier keys to create a layer for numeric values. So, when I press a modifi…

What I am trying to say is that operating system should collate events from all keyboards, so that wouldn't matter which one had modifier pressed on.
Post reply on HN