> how does Xournal compare to OneNote?
It doesn't compare. At all. It's like notepad.exe vs vim. But if you just need a paper/pen replacement, it gets the job done fine.
> use touch for scrolling or zooming and maybe have gestures for right/middle click as well as an easy to access on-screen keyboard.
The only DE/toolkit that supports finger scrolling out of the box is Gnome/GTK3. So if you limit yourself to new GTK3 programs, you should be fine (well, relatively).
If you stray outside of that, you're in "finger as mouse" land, and you can only try and improve things with things like this and this. AFAIK, the default X config gives you two-finger scrolling, pinch to zoom as well as right click support (while holding an object with one finger, tap anywhere else on the screen), but it's really clunky and requires very deliberate movements.
Onboard is the best on-screen keyboard I've found, but it's severely lacking compared to most Android keyboards.
Personally, I just use i3 (with the rotate button toggling easystroke's gesture recognition) and use the stylus exclusively with xournal. I have a dual-boot setup with Android-x86 for when I want to play touchscreen games, etc.
There are multiple answers to this question: 1. On the one hand, Fly-Pie is primarily designed to be used with one hand at the keyboard and one hand at your mouse. Executing a simple shortcut like Super+Space with your left hand and then moving your mouse in a specific direction to simulate a complex shortcut like Ctrl+Shift+Alt+Left (which is impossible to press with one hand only) is a valid use case. 2. On the other hand, there are many ways to open open menus beyond pressing keyboard shortcuts as Fly-Pie has a command line API to open menus. * CustomCorner: Open menus by moving your mouse to one corner of your screen! * Easystroke: X11 only, use mouse gestures to open menus! * xbindkeys: X11 only, bind menus to your additional mouse buttons!
Lastly, if you have one of these mice with programmable buttons, you can make the buttons of your mouse simulate a shortcut to open a menu. This feels really awesome as you can simply draw a gesture with this button!
There are quite a few ways to open menus beyond pressing keyboard shortcuts as Fly-Pie has a command line API to open menus. Here are some examples, but this list can be extended by creative people, I guess :) * CustomCorner: Open menus by moving your mouse to one corner of your screen! * Easystroke: X11 only, use mouse gestures to open menus! * xbindkeys: X11 only, bind menus to your additional mouse buttons!
Lastly, if you have one of these mice with programmable buttons, you can make the buttons of your mouse simulate a shortcut to open a menu. This feels really awesome as you can simply draw a gesture with this button!
try easystroke. it has also seen no development since 2016, but still apparently works (with the help of numerous unmerged patches) and is popular.
read https://github.com/thjaeger/easystroke/wiki/BuildInstructions on how to get a patched version. there are patched debs and appimages available.
I took a software approach for that.
Web Browser:
I use an old XUL addon in my web browser (Palemoon) called FireGestures.
Outside of the web browser:
I also use an application called Easystroke. It's for X11 desktops, so think of like Ubuntu and such. I prefer FireGesutres specifically for my browser, however you can use Easystroke with any application; no browser addons necessary!
I pretty much use the same gestures for my file manager or anything else with a forward/back function, except Easystroke doesn't support rocker gestures so I use hold RMB swipe left & right in place of it.
The scroll wheel does feel a bit cheap, but I have the scroll sensitivity adjusted so it doesn't fly. I'll often use auto scrolling though by clicking in the middle button and pointing the cursor to where I want it to scroll if it's going to be a long scroll (which is sort of what it was intended for, but people forgot.) Smaller scrolls and I'll use the wheel.
Installing glibmm-devel was the 1st thing I did, but the identical msg still shows up. As well, I've installed a bunch of other things emulating the easystroke installs on other linux systems outlined here: https://github.com/thjaeger/easystroke/wiki/BuildInstructions
But I think my problem is the compiler can't see them even after I've installed them. I need to put them somewhere else or set path, which I will look into as it seems like such a trivial step. Or I could put in a request to have easystroke included in the repository.
Its true power is shown when used with (patched) easystroke: http://askubuntu.com/a/843560/418443
Easystroke: https://github.com/thjaeger/easystroke/wiki
If you would to try it, here's my PR to easystroke: https://github.com/thjaeger/easystroke/pull/9
For anyone else looking for a solution to this problem, I've managed to pull off "hands free" scrolling by xinput/xorg binding a button on my trackball mouse to draglock and then setting easystroke to scroll when Alt key + draglock button are tapped.
The end of result is no more hold-down-button to scroll, system-wide ;-) Resource usage is on par with emulated scroll wheel of Xorg so a win-win so far.