Guido Günther @agx@librem.one

@bragefuglseth good point, that was supposed to go around the list box only and I added the search entry later on. Should be better now. Thanks!

One thing that bugged me is that we had no way in #phosh to present only the available OSK layouts to the user to pick from. This led to confusion as users configured a layout which then would not be available later on. phosh-osk-stub can now provide that information to mobile settings (and it will be simple to add support for e.g. squeekboard if it dumps out the relevant information).

Thanks to #libadwaita and #GTK4's list models such things are fun to add.

@matt can the versions used for gtk4-rs be a sensible baseline? That isn't easy to package for Debian either but so far Debian's Rust maintainers always got it in.

@chfkch @helix @phosh @devrtz

(one of the few cases where the sequel is just as good as the first movie).

Be excellent to each other!

@cas @fizzo they're tracked but the way we grab events doesn't let those bubble up (see the linked issue).

@wannoye I don't think there's one in squeekboard yet: https://gitlab.gnome.org/World/Phosh/squeekboard/-/tree/main/data/keyboards?ref_type=heads - maybe you want to file an issue or provide one?

There's one in phosh-osk-stub if you want to try another keyboard.

@dubstar_04

And as @praveen
said: lots of issues are hardware specific so Phosh will benefit a lot by getting wider hardware support. I'd say the varying support over devices is what hits us the most atm as the experience differs so much.

2/2

@dubstar_04
@praveen

We're following the discussions. Phosh has a recommended (codified) set of apps/services we ship by default and we preferably develop for / contribute to. That is unlikely to change based on a poll. It can change based on good arguments so I hope to learn some of those during the ongoing discussions (and also learn about gaps that people are currently bridging with workarounds or that we missed completely so far).

1/2

@fizzo That's related to the way how we currently handle the touch events (so not OP6 specific) so an issue would be helpful.

llibphosh-rs 0.0.2 is up at https://crates.io/crates/libphosh . Thanks to @me for making it compatible with #phosh 0.41 .

This is hopefully the first release 🐸 can use out of the box.

@arunmani @suraj_sloth Thanks! That didn't work when I posted it as it was a live stream still. Just wanted to update and saw it's already there 🙏

(I also only noticed during the presentation that @rudraps is on stage too)

Too bad this mastodon instance doesn't allow edits: Gotam's fedi handle is @gauthamx

@janvlug @eliasr @devrtz

Yup, better not do that (`dpkg --force-depends` would work to remove system chatty temporarily but it'll get pulled back in on updates).

Another option is to move away /etc/xdg/autostart/sm.puri.Chatty-daemon.desktop when running the flatpak (which AFAIK does not get autostarted on boot so you might not get new SMS).

Chatty is tightly integrated into the system on phones, I think the flatpak is currently more of a demo for systems where it's not running yet.

@docRekd @eliasr It took us a long time to make Linux work on PC, servers and laptops either but it grows device by device and if you include the Halium based devices there's quiet a few already. It will just be the new normal at some point.

@eliasr @janvlug @devrtz I would even uninstall the system chatty as otherwise two processes try to take SMS out of the Modem. (and after uninstalling make sure there's no process running).

@janvlug @devrtz Looks like you had the system instance still running (starting chatty would then just activate that one).

@suraj_sloth and Gotam talking about #phosh at OOSC (https://oosc-next.vercel.app/):

https://www.youtube.com/watch?v=dDZJ1d-n2xg