~earboxer

West Michigan, USA

https://zachdecook.com

We start, around the turn of the millenium, with a dot on the map: a small city where tickets to the local cinema cost only two dollars. Just outside city limits sat a parsonage, inwhich memorable history was being formed:

"That's so easy, even Zach can read it!" called one of the others.

Now, others there were, in contrast to the big people, who, here, seemed to run the joint by joint-ownership.

I was beckoned toward a newspaper, where a three-panel cartoon was being indicated.

"Here, read this!"

My first test of skill... would I succeed, proving my capability, or fail, showing the known universe that I was most inferior.

Panel 1: Garfield sits on the counter, saying "Zzzzzzzz" Panel 2: Garfield is still sitting on the counter, Jon is watching. Garfield says "Zzzzzzzz" Panel 3: Jon breaks the pattern of Zee's, and says ________...

I couldn't do it. I was the only person who didn't know how to read.

Trackers

~earboxer/statusbar

Last active 1 year, 14 days ago

~earboxer/sxmo-icons

Last active 2 years ago

#594 Enhancement: Consider using iio-sensor-proxy for rotation and proximity monitoring 3 months ago

Comment by ~earboxer on ~mil/sxmo-tickets

Alternatively for SDM845 devices, we can use libssc's ssccli with these patches: https://codeberg.org/DylanVanAssche/libssc/pulls/22

and a cleaned up version of this change to sxmo_proximitylock.sh

https://paste.sr.ht/~earboxer/ebb08a8782e52ae54653491004eabf7bff1a6352

#473 accessibility: screen-reader (text-to-speech) in menu 5 months ago

Comment by ~earboxer on ~mil/sxmo-tickets

90% of this would be to use an accessible picker in place of bemenu. (read the title, then read the currently selected item)

Sxmo would need an env variable to switch the menu command.

Other things that could already be done:

  • switch SXMO_TERMINAL to an accessible terminal emulator (this exists, right?)--or perhaps one with brltty set up in it?
  • set KEYBOARD_ARGS to something that would pipe typed keys into espeak or similar?
  • override the inputhandler hook to announce what each gesture is doing?
  • throw together a script for reading the status...

(After getting these tasks done, pmos could make another package to ship these overrides)

All we need is someone who is willing to do the work and someone who is able to determine it works adequately.

#112 Incoming texts with unicode content don't display 8 months ago

Comment by ~earboxer on ~mil/sxmo-tickets

~bsduck: ~stacyharper fixed it in 2c0c56df. (which hasn't yet been tagged). You could apply that patch locally, or run master to get the latest fixes.

#574 KISS multi-button-presses goodbye 8 months ago

Comment by ~earboxer on ~mil/sxmo-tickets

You can find my non-multikey patch at https://paste.sr.ht/~earboxer/7e92f3084752bfb29258a3255bbf5e59252ee4d7 , (might be a good starting place?)

(I like it enough, but miss voldown_two and volup_three)

(we'll, of course also need a documentation patch after we stick with some approach).

#574 KISS multi-button-presses goodbye 11 months ago

Comment by ~earboxer on ~mil/sxmo-tickets

I've been running this daily for a few days, and I really like the snappy-ness of the instant feedback for opening the menu and toggling the keyboard. I think a lot of my frustration has come from my device's power button having some "chatter"/noise when I press it (it sometimes presses itself a second time when I'm releasing the button). (so by keeping it "simple", I was able to discover this hardware fault more easily).

voldown_two: in the ticket, I said it could be mimicked with super+e, which is somewhat incorrect (it toggles from horizontal to vertical split). super+w goes into "tabbed" mode in sway. Personally I'm fine doing it with the keyboard, since it's not too frequent that I'm running more than four apps.

voldown_three: we've long since had the two fingers down and three fingers down to close/kill a program. My comment above for the shortcut was wrong, its super+shift+q to kill the running app.

An alternative proposal would be to keep the instant 'tap' commands, but allow 'longhold-release' to also execute something. So pressing volumedown would toggle the keyboard, but if you held it, then releasing would kill the current app.

pressing volume up could open the menu, but if you held it, then releasing would close that menu and open the wmmenu.

(nothing would be added to the powerbutton, because the dpms commands already take up to half a second).

Of course, this point of this ticket is "Simplicity", which this second proposal doesn't serve, so I'll pretend I never thought of it.

#574 KISS multi-button-presses goodbye 11 months ago

Ticket created by ~earboxer on ~mil/sxmo-tickets

#Motivation

multi-button presses is often one of the first pain-points for new users. When I first started using sxmo, I would frequently long-press one of the buttons when I meant to just tap it (which, for three_button_touchscreen, is the difference between opening the keyboard and killing the current application).

Some discrepancies between timing, performance, and behavior between DWM and Sway led to the development of bonsai, which allows you to configure "complex keybinds". (and due to hare's lack of broad architecture support, SXMO never fully transitioned to bonsai).

Complex is the opposite of simple, the moniker of this project. We should have simple defaults (and those who want complex keybinds can add bonsai or whatever).

I currently have some bugs with my setup where my screen randomly locks when I'm in a menu, so I think the current code is already broken.

#Challenges

What to do with the old commands?

We should provide alternatives for any important functionality we're removing.

  • powerbutton_two: This is already the same as doing powerbutton twice.
  • powerbutton_three:
    • we need to come up with a better way of managing proximity_lock (already needing a command to kill it means it gets started out of control (on devices without prox sensors))
    • opening the terminal can be done with super+enter on the keyboard. Maybe a gesture should be created to do this. (when no apps are in the current workspace?)
  • volup_two: jumping from appmenu to sysmenu is pretty easy already
  • volup_three: we should add a gesture to access sxmo_wmmenu.sh (and maybe add a keyboard shortcut for it too?)
  • voldown_two: layout can be toggled using the keyboard (super+e), or via sxmo_wmmenu.sh (which we should add a gesture for)
  • voldown_three: windows can be killed with a keyboard shortcut (super+q), or a gesture

#What about one_button_e_reader???

  • powerbutton_two: keyboard can be opened with a gesture
  • powerbutton_three: windows can be killed with keyboard shortcut or a gesture.

#3 Package this in distributions 1 year, 14 days ago

Ticket created by ~earboxer on ~earboxer/statusbar

My attempt to do this in Alpine: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/38968

(Creates the font configs so that 'statusbar' refers to the patched font with a fallback on the parent font, has dependencies so that you can install just statusbar and you'll get whatever statusbar matches the fonts you have installed.)

(I put packaging effort on hold to update this project with more icons)

#1 Make volume icons when volume is clipping 1 year, 14 days ago

Comment by ~earboxer on ~earboxer/statusbar

REPORTED RESOLVED IMPLEMENTED

#509 Zach's grand plan for ditching nerd fonts icons forever. 1 year, 2 months ago

Comment by ~earboxer on ~mil/sxmo-tickets

If anyone (~baroque0) wants to help creating SVG icons, see https://todo.sr.ht/~earboxer/statusbar to see what additional icons I wanted to add before sending my next iteration of the patch.

#2 Make volume icons for headphones 1 year, 2 months ago

Ticket created by ~earboxer on ~earboxer/statusbar

showing different amounts of volume coming out of the headphones.