Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
p12tic
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
p12tic
5y ago
All of these are great, but perhaps the most important would be money as it's the only thing that clearly indicates the level of community support. Once there's funding it's much easier to prioritize the work. I've setup
32.
▲
by
p12tic
5y ago
I've created a Patreon page: https://www.patreon.com/p12tic . Thanks!
33.
▲
by
p12tic
5y ago
It seems like there's at least some interest, you were the one that pushed me over the fence :-) I've created a Patreon page: https://www.patreon.com/p12tic . I think it does not make sense to involve X.org as we a
34.
▲
by
p12tic
5y ago
I think something around $4000 monthly would be enough for release management duties and minimal maintenance. Of course just one person part-time is not enough for large-scale changes, but for resolving regressions and just making sure cont
35.
▲
by
p12tic
5y ago
> though you're not clear whether it's time, money or community you're asking for All of these, but perhaps the most important would be money as it's the only thing that clearly indicates the level of community suppor
36.
▲
by
p12tic
5y ago
On Debian it's the same. I use Debian packages as the means to ship code to test devices and the most time consuming thing when converting X server from autotools to meson was the default configure flags (meson and autotools use diffe
37.
▲
by
p12tic
5y ago
My own experience working on X server, clean ccache-based rebuild is a couple minutes faster on meson compared to autotools. These minutes add up quickly, switching my workflow to meson paid for itself the same day.
38.
▲
by
p12tic
5y ago
At least I would not have been driving this release. Maybe someone else would have stepped up, it's hard to say. However there was no release manager for the last several years, so the likelihood of this outcome would have been small.
39.
▲
by
p12tic
5y ago
Hi, I'm the release manager responsible for this X release seeing the light. This release would not have happened if an effort to improve touchpad support in Linux was not funded for the past year and half. X server 21.1 makes touchpad
40.
▲
X.org Server 21.1 RC1 Released
(phoronix.com)
6 points
by
p12tic
5y ago
|
0 comments
41.
▲
Linux Touchpad like MacBook: Touchpad gestures land to Qt, Gimp and X server
(bill.harding.blog)
33 points
by
p12tic
5y ago
|
3 comments
42.
▲
by
p12tic
6y ago
Hey, thanks for interest in donating to the project. I'm Povilas, the developer from the linked blog post. If the donation is less than $100 you could setup a monthly donation on GitHub and then cancel it after the first payment. Other
43.
▲
by
p12tic
6y ago
Whoops, I forgot the link to the results of the poll: [1]: https://bill.harding.blog/2020/06/22/linux-touchpad-project-...
44.
▲
by
p12tic
6y ago
I haven't asked this question unfortunately. Adding touchpad gestures needs changes in every GUI toolkit library except GTK and every application we would like to support. So I trusted my own experience of seeing the amount of effort n
45.
▲
by
p12tic
6y ago
Povilas from the linked blog post here. The reasons why we chose the current path were explained in detail in the blog posts. Touchpad gestures was the most popular feature to implement. In order to do that we needed a good reason why all t
46.
▲
by
p12tic
6y ago
Fixing issues like this is the primary goal of this project. Unfortunately there's a long way to go.
47.
▲
by
p12tic
6y ago
Currently we're focusing on touchpad gestures (i.e. multi-finger touch swipe or pinch) as the poll [1] made in June indicated that touchpad gestures was the most wanted feature. There's plenty of work just implementing the basic h
48.
▲
by
p12tic
6y ago
Povilas from the linked blog post. Indeed this is a valid point, thanks. On the X server applications will get touchpad gestures regardless of whether one is running Plasma or GNOME. However, workspace-wide gestures are not implemented in e
49.
▲
by
p12tic
6y ago
I think you should thank Peter Hutterer for his contributions to libinput. I'm just a random developer who loves complex problems and free software and was also interested in trying to improve Linux touchpad support :-)
50.
▲
by
p12tic
6y ago
> AFAIK GTK4 will be Wayland-only and out in a few months I think this is incorrect. See the following, X11 backend is listed among supported backends. https://developer.gnome.org/gtk4/stable/extra-configuration
51.
▲
by
p12tic
6y ago
Say you have a widget toolkit that doesn't support touchpad gestures. The maintainers of that widget toolkit would be more willing to integrate this feature if there's support in both Xorg and Wayland compared to Wayland alone.
52.
▲
by
p12tic
6y ago
> To be clear, you're saying that implementation in the applications/toolkits ecosystem is the barrier to a better trackpad experience on Linux and that by unifying the feature set of both X and Wayland, this will encourage tha
53.
▲
by
p12tic
6y ago
Povilas from the linked blog here. In open source often no one really cares about a suggested feature or even a submitted pull requests. It means additional work for the project maintainers - discussing design, reviewing code and handling o
54.
▲
by
p12tic
6y ago
Our work on X will expose enough information to the window manager and the applications to implement workspace switching in the way you describe. Fusuma is not integrated with the display server, so it's limited in what it can do.
55.
▲
by
p12tic
6y ago
Povilas from the linked article. It's not obvious, but adding touchpad gesture support to X will benefit you too even if you're not using X. This will make our work of convincing the maintainers of other open source projects much
56.
▲
by
p12tic
6y ago
Povilas from the linked article here. Having support in X (even if only in proposal stage) will allow much easier work in the toolkit and application layers. X and Wayland cover essentially al Linux users, so we will not need to estimate ho
57.
▲
by
p12tic
6y ago
Povilas from linked article here. The design of how libinput handles gestures is exactly like you describe - the application will get a Start event when a gesture is identified, an Update event when finger position change and an End event w