The first patch is a refactorisation to help on the second patch.
This is still to be considered WIP. It works well, but the UI doesn't
feels polished. I'd like to no add any additional bemenu folder. If you
have recommendations \o/
[PATCH sxmo-utils 1/2] sxmo_hook_sms.sh: use a return fast form
Are there issues left with this besides the ui? If not can we merge it
and figure out that ui later?
> + fi> + if [ -f "$XDG_CONFIG_HOME"/sxmo/.busy ]; then> + printf " %s Busy ^ rm -f \"$XDG_CONFIG_HOME\"/sxmo/.busy\n" "$icon_ton"> + else> + printf " %s Busy ^ touch \"$XDG_CONFIG_HOME\"/sxmo/.busy\n" "$icon_tof"> + printf " %s Busy for 15 min ^ date '+%%s+15*60' | bc > \"$XDG_CONFIG_HOME\"/sxmo/.busy\n" "$icon_tmr"> + printf " %s Busy for 30 min ^ date '+%%s+30*60' | bc > \"$XDG_CONFIG_HOME\"/sxmo/.busy\n" "$icon_tmr"> + printf " %s Busy for 1 hour ^ date '+%%s+60*60' | bc > \"$XDG_CONFIG_HOME\"/sxmo/.busy\n" "$icon_tmr"> + printf " %s Busy for 2 hour ^ date '+%%s+2*60*60' | bc > \"$XDG_CONFIG_HOME\"/sxmo/.busy\n" "$icon_tmr"> + printf " %s Busy for 3 hour ^ date '+%%s+3*60*60' | bc > \"$XDG_CONFIG_HOME\"/sxmo/.busy\n" "$icon_tmr"
Would it be possible to handle custom time periods? Perhaps we could
borrow the duration logic from the wakelock code and use the same
format?
I think this might require a sub-menu to avoid extra complexity with
parsing. Does adding that help clarify how the ui should look at all?
> + fi> }> > menuchoices() {> -- > 2.45.1>
Re: [PATCH sxmo-utils 2/2] sxmo_audio.sh: add a busy mode
Hey Aren,
> Are there issues left with this besides the ui? If not can we merge it> and figure out that ui later?
No, this still works well.
> > + fi> > + if [ -f "$XDG_CONFIG_HOME"/sxmo/.busy ]; then> > + printf " %s Busy ^ rm -f \"$XDG_CONFIG_HOME\"/sxmo/.busy\n" "$icon_ton"> > + else> > + printf " %s Busy ^ touch \"$XDG_CONFIG_HOME\"/sxmo/.busy\n" "$icon_tof"> > + printf " %s Busy for 15 min ^ date '+%%s+15*60' | bc > \"$XDG_CONFIG_HOME\"/sxmo/.busy\n" "$icon_tmr"> > + printf " %s Busy for 30 min ^ date '+%%s+30*60' | bc > \"$XDG_CONFIG_HOME\"/sxmo/.busy\n" "$icon_tmr"> > + printf " %s Busy for 1 hour ^ date '+%%s+60*60' | bc > \"$XDG_CONFIG_HOME\"/sxmo/.busy\n" "$icon_tmr"> > + printf " %s Busy for 2 hour ^ date '+%%s+2*60*60' | bc > \"$XDG_CONFIG_HOME\"/sxmo/.busy\n" "$icon_tmr"> > + printf " %s Busy for 3 hour ^ date '+%%s+3*60*60' | bc > \"$XDG_CONFIG_HOME\"/sxmo/.busy\n" "$icon_tmr">> Would it be possible to handle custom time periods? Perhaps we could> borrow the duration logic from the wakelock code and use the same> format?>> I think this might require a sub-menu to avoid extra complexity with> parsing. Does adding that help clarify how the ui should look at all?
Yes but I'd like to avoid sub-menus. Particularly in that one, with
entries that are not typeable by the user anyway.
But yes, to make busy timeout typeable to the user, probably we have to
add a dedicated menu.
Merging, this seems like a good feature to have, and we can polish the
UI later.
During testing I noticed that the notification sounds are still played
for incoming texts, I'm not sure if that's intentional.
To git.sr.ht:~mil/sxmo-utils
20a89df..23617f1 23617f1 -> master
On Fri, May 31, 2024 at 06:41:34PM GMT, Willow Barraco wrote:
> The first patch is a refactorisation to help on the second patch.> > This is still to be considered WIP. It works well, but the UI doesn't> feels polished. I'd like to no add any additional bemenu folder. If you> have recommendations \o/>