✨ New Feature: Touchscreen scrolling #594

markstos commented 2025年06月22日 16:42:59 +02:00

No description provided.

proycon commented 2025年06月22日 17:32:52 +02:00

Thanks for the quick implementation! This already looks quite promising. The actual main thing that is still missing now is the ability to tap/select using touch.

Also I think the direction of the scrolling could better be reversed. I've attached two videos to show the behaviour on a touchscreen, the first is fuzzel with this patch, the second is wofi (which has touch behaviour I find quite intuitive).

Thanks for the quick implementation! This already looks quite promising. The actual main thing that is still missing now is the ability to tap/select using touch. Also I think the direction of the scrolling could better be reversed. I've attached two videos to show the behaviour on a touchscreen, the first is fuzzel with this patch, the second is wofi (which has touch behaviour I find quite intuitive).

markstos commented 2025年06月22日 19:33:44 +02:00

Thanks for the feedback. I've pushed another commit with the following changes:

1. Reversed scrolling direction
2. Tap-to-select functionality
3. Smoother scrolling with momentum

Thanks for the feedback. I've pushed another commit with the following changes: 1. Reversed scrolling direction 2. Tap-to-select functionality 3. Smoother scrolling with momentum

proycon commented 2025年06月22日 20:19:24 +02:00

Awesome! This works great already!

Awesome! This works great already!

markstos commented 2025年06月22日 20:27:06 +02:00

@proycon Great! Could you share another short video of Fuzzel's touchscreen support in action? And could I have permission to use it in a blog post featuring interesting uses of Fuzzel's new features?

I noticed you are using the default theme. We are working refreshing that over here: #561 The new theme will probably get a refined a bit further from what's there.

And could you say more why Fuzzel is of interest to replace bemenu in the SXMO project?

@proycon Great! Could you share another short video of Fuzzel's touchscreen support in action? And could I have permission to use it in a blog post featuring interesting uses of Fuzzel's new features? I noticed you are using the default theme. We are working refreshing that over here: https://codeberg.org/dnkl/fuzzel/issues/561 The new theme will probably get a refined a bit further from what's there. And could you say more why Fuzzel is of interest to replace bemenu in the SXMO project?

markstos commented 2025年06月22日 20:42:00 +02:00

And @proycon Would the "disable prompt" feature being requested also help for building mobile touch-friend menus with Fuzzel?

430

And @proycon Would the "disable prompt" feature being requested also help for building mobile touch-friend menus with Fuzzel? [430](https://codeberg.org/dnkl/fuzzel/issues/430)

proycon commented 2025年06月22日 22:34:59 +02:00

Great! Could you share another short video of Fuzzel's touchscreen
support in action? And could I have permission to use it in a blog post
featuring interesting uses of Fuzzel's new features?

Sure! I recorded a new video, this time on a phone and with the new theme. That might make for a nice demo video, feel free to use! (CC-BY) (tip: the new theme indeed looks a lot better, but contrast between selected row and background could be improved still I think)

And @proycon Would the "disable prompt" feature being requested also help for building mobile touch-friend menus with Fuzzel?

In most cases we do retain the prompt with input bar, but we probably also have some edge-cases where it would be nice not to have one.

And could you say more why Fuzzel is of interest to replace bemenu in
the SXMO project?

Bemenu's nice (also the fact that is has different backends) but its scrolling behaviour (paging) is sub-optimal. Wofi's scrolling behaviour is the best but it relies on all of gtk whereas we like leaner solutions generally. Wofi's maintenance status might > Great! Could you share another short video of Fuzzel's touchscreen

support in action? And could I have permission to use it in a blog post
featuring interesting uses of Fuzzel's new features?

Sure! I recorded a new video, this time on a phone and with the new theme. That might make for a nice demo video, feel free to use! (CC-BY) (tip: the new theme indeed looks a lot better, but contrast between selected row and background could be improved still I think)

And @proycon Would the "disable prompt" feature being requested also help for building mobile touch-friend menus with Fuzzel?

In most cases we do retain the prompt with input text, but we probably also have some edge-cases where it would be nice not to have one.

And could you say more why Fuzzel is of interest to replace bemenu in
the SXMO project?

Bemenu's nice (also the fact that is has different backends) but its scrolling behaviour (paging) is sub-optimal. Wofi's scrolling behaviour is the best but it relies on all of gtk whereas we like leaner solutions generally. Wofi's maintenance status might also become an issue. Fuzzel seemed a leaner alternative so peeked my interest but without touch support it wasn't an option yet. Now it is! Thanks! :)

Once fuzzel with this touch support is released, I'll work on a patch for sxmo. Users themselves can then choose what menu they prefer, it's all fairly easily exchangeable as long as some dmenu-like conventions are adhered to.

become an issue. Fuzzel seemed a leaner alternative so peeked my interest.

Once fuzzel with this touch support is released, I'll work on a patch for sxmo. Users themselves can then choose what menu they prefer, it's all fairly easily exchangeable as long as some dmenu-like conventions are adhered to.

> Great! Could you share another short video of Fuzzel's touchscreen > support in action? And could I have permission to use it in a blog post > featuring interesting uses of Fuzzel's new features? Sure! I recorded a new video, this time on a phone and with the new theme. That might make for a nice demo video, feel free to use! (CC-BY) (tip: the new theme indeed looks a lot better, but contrast between selected row and background could be improved still I think) > And @proycon Would the "disable prompt" feature being requested also help for building mobile touch-friend menus with Fuzzel? In most cases we do retain the prompt with input bar, but we probably also have some edge-cases where it would be nice not to have one. > And could you say more why Fuzzel is of interest to replace bemenu in > the SXMO project? Bemenu's nice (also the fact that is has different backends) but its scrolling behaviour (paging) is sub-optimal. Wofi's scrolling behaviour is the best but it relies on all of gtk whereas we like leaner solutions generally. Wofi's maintenance status might > Great! Could you share another short video of Fuzzel's touchscreen > support in action? And could I have permission to use it in a blog post > featuring interesting uses of Fuzzel's new features? Sure! I recorded a new video, this time on a phone and with the new theme. That might make for a nice demo video, feel free to use! (CC-BY) (tip: the new theme indeed looks a lot better, but contrast between selected row and background could be improved still I think) > And @proycon Would the "disable prompt" feature being requested also help for building mobile touch-friend menus with Fuzzel? In most cases we do retain the prompt with input text, but we probably also have some edge-cases where it would be nice not to have one. > And could you say more why Fuzzel is of interest to replace bemenu in > the SXMO project? Bemenu's nice (also the fact that is has different backends) but its scrolling behaviour (paging) is sub-optimal. Wofi's scrolling behaviour is the best but it relies on all of gtk whereas we like leaner solutions generally. Wofi's maintenance status might also become an issue. Fuzzel seemed a leaner alternative so peeked my interest but without touch support it wasn't an option yet. Now it is! Thanks! :) Once fuzzel with this touch support is released, I'll work on a patch for sxmo. Users themselves can then choose what menu they prefer, it's all fairly easily exchangeable as long as some dmenu-like conventions are adhered to. become an issue. Fuzzel seemed a leaner alternative so peeked my interest. Once fuzzel with this touch support is released, I'll work on a patch for sxmo. Users themselves can then choose what menu they prefer, it's all fairly easily exchangeable as long as some dmenu-like conventions are adhered to.

markstos commented 2025年06月22日 23:36:43 +02:00

@proycon I went ahead and implementing the --hide-prompt option, which I think will also be a good fit for touchscreens. You can see a screenshot and try it here. That branch also includes the touchscreen commits so you can test them together. #596

@proycon I went ahead and implementing the --hide-prompt option, which I think will also be a good fit for touchscreens. You can see a screenshot and try it here. That branch also includes the touchscreen commits so you can test them together. #596

dnkl commented 2025年06月23日 10:53:39 +02:00

Oh, we'd also want a changelog entry!

Oh, we'd also want a changelog entry!

markstos commented 2025年06月23日 18:11:24 +02:00

assume it's based on foot's implementation?

I used Warp terminal, which in turn used Claude 4, which in turn could have quite possibly referenced foot's implementation.

> assume it's based on foot's implementation? I used Warp terminal, which in turn used Claude 4, which in turn could have quite possibly referenced foot's implementation.

markstos commented 2025年06月23日 18:16:56 +02:00

I added a code comment about the block @dnkl asked about, mentioned touchscreen support in the README along with mouse support and updated the Changelog.

I added a code comment about the block @dnkl asked about, mentioned touchscreen support in the README along with mouse support and updated the Changelog.

diederik commented 2025年09月10日 14:20:35 +02:00

Oh wow! I recently learned about fuzzel and it looks interesting. I wanted to get some experience with it first before potentially asking whether it could possibly be used on mobile devices ... thus touchscreen support.
To find you already have that implemented \o/

Oh wow! I recently learned about fuzzel and it looks interesting. I wanted to get some experience with it first before potentially asking whether it could possibly be used on mobile devices ... thus touchscreen support. To find you already have that implemented \o/

markstos commented 2025年09月10日 16:47:37 +02:00

@diederik There's a video linked in the issue above demonstrating Fuzzel being used on a mobile device.

@diederik There's a video linked in the issue above demonstrating Fuzzel being used on a mobile device.

diederik commented 2025年09月10日 17:03:29 +02:00

@markstos I saw it. Initial impression of @proycon's video of wofi looked smoother though as the 'feedback' seemed more direct with the finger movements.
But I guess there's no better way to experience it then trying it out myself ;-)

May take a bit though as I've got a lot to learn; I haven't used/or configured sway and associated tools (like fuzzel) much.
Mostly been working on getting hardware to function (better) thus far. (relevant for touch: PineTab2, but ultimate goal is the PineNote)

First challenge: how to invoke it (without keyboard)

@markstos I saw it. Initial impression of @proycon's video of wofi looked smoother though as the 'feedback' seemed more direct with the finger movements. But I guess there's no better way to experience it then trying it out myself ;-) May take a bit though as I've got a lot to learn; I haven't used/or configured sway and associated tools (like fuzzel) much. Mostly been working on getting hardware to function (better) thus far. (relevant for touch: PineTab2, but ultimate goal is the PineNote) First challenge: how to invoke it (without keyboard)

diederik commented 2025年09月10日 17:08:48 +02:00

Currently reading through your blog :-D (and installing fuzzel everywhere)

Currently reading through your blog :-D (and installing ``fuzzel`` everywhere)

brianmercer commented 2025年10月18日 17:32:25 +02:00

Thanks for the touch screen support.

It would be great if the scrolling action would conform to more typical touch screen behavior by moving the scroll bar and not the selected item.

In other apps, swiping up and down just scrolls the list. It might also select, but without activating.

In a touch menu, I'd probably change the selected item color to transparent, since I don't think I'm ever going to use up and down arrows to select items.

Also, touch outside the window should close the window since there's no close button and the esc key might not be available.

Thanks! Been using wofi, but I don't love it. fuzzel could be first class in touchscreen.

Thanks for the touch screen support. It would be great if the scrolling action would conform to more typical touch screen behavior by moving the scroll bar and not the selected item. In other apps, swiping up and down just scrolls the list. It might also select, but without activating. In a touch menu, I'd probably change the selected item color to transparent, since I don't think I'm ever going to use up and down arrows to select items. Also, touch outside the window should close the window since there's no close button and the esc key might not be available. Thanks! Been using wofi, but I don't love it. fuzzel could be first class in touchscreen.

brianmercer commented 2025年10月18日 18:02:36 +02:00

Dunno anything about implementations, but regarding foot above.

Foot does scroll on swipe up and down, bit only in a fixed way while holding contact.

I use ptyxis which implements the flick motion like on an android phone or in gtk. fuzzel currently does move on a flick, but doesn't continue to travel while slowing the scroll speed.

And a third request to mimic typical behavior: scrolling needs to stop at the top and bottom and not rollover.

Thanks!

Dunno anything about implementations, but regarding foot above. Foot does scroll on swipe up and down, bit only in a fixed way while holding contact. I use ptyxis which implements the flick motion like on an android phone or in gtk. fuzzel currently does move on a flick, but doesn't continue to travel while slowing the scroll speed. And a third request to mimic typical behavior: scrolling needs to stop at the top and bottom and not rollover. Thanks!

markstos commented 2025年10月26日 00:02:32 +02:00

@brianmercer You are commenting on a closed pull request. If you want more touch features, please open a new issue to discuss each change request.

@brianmercer You are commenting on a closed pull request. If you want more touch features, please open a new issue to discuss each change request.