Guido Günther @agx@librem.one

@cas I think the emphasis should be on *hardware* not *kill*. In a world where software tries to be clever physical switches (that are easily operated without even looking at the device) off means of and on means on which is very reassuring when one wants to save power or make sure one doesn't accidentally hit immense roaming fees with wwan on.

More info on GtkInspector in #gnome's developer documentation: https://developer.gnome.org/documentation/tools/inspector.html and here's how to use it in a nested phosh session: https://phosh.mobi/posts/phosh-dev-part-0/

Another small detail: I often need to scroll up in #chatty to reread something when composing a msg. Going back to the last msg of the conversation by taping the 🔵 would close the ⌨️ forcing me touch into the text area again (and causing visual distraction). We can fix this by having the 🔵 not take focus.

Posting this to demo it can be a one line change in a UI file to make #LinuxMobile work better. So please get involved! #Gtk 's GtkInspector is great to figure such things out.

#phosh

@kirschner It's in #debian already (thanks to the awsome #Rust packaging team) https://packages.debian.org/trixie/railway-gtk (and also on #flathub)

@chfkch I think it's a matter of setting `content-height`, e.g.

+ <property name="content-height">400</property>

should make it "movable". Basically the content height needs to be low enough to fit the screen when the OSK is shown.

Idk if that's the currently best solution as the dialog then also doesn't take full height on large screens.

@kirschner For #LinuxMobile phones there's #Railway : https://mobile.schmidhuberj.de/railway

Maybe it would be useful if the apps could display the QR Code?

@okias Nah, I'm just standing on the shoulders of giants here (but thanks!). 😄

@eliasr @devrtz …and we need the DBus activation in chatty for push notifications too.

@eliasr as chatty and calls run as daemon on session startup: so should it be slow for large call histories / room lists we can tweak that by preloading those. @devrtz already optimized that in calls a while back by only loading parts of the history. So basically startup was seemingly slow (although the app was already up) because calls/chatty didn't notify the rest of the system with a valid token

@eliasr Both were running in the background already but the activation token to tell the compositor: hey, I'm here and should get focus (because phosh said so) was lost in the phosh -> spawns calls -> spawned calls instance notifies "calls daemon" that a window should be shown (and then quits) chain of events. By switching to DBus activation we remove the intermediate calls instance, the token gets passed and the compositor knows that calls is up (same for chatty).

It's the small things: If you've been bothered with #calls and #chatty seemingly starting up slowly in #phosh (while most other apps startup fast): I've posted MRs to fix this in chatty and calls (which then also prompted a small fix in phosh). Here's a quick demo of calls before and after the change:

MRs:
- calls: https://gitlab.gnome.org/GNOME/calls/-/merge_requests/760
- chatty: https://gitlab.gnome.org/World/Chatty/-/merge_requests/1432

@Blort That's the thing, with the current rope we have we can just take what the text input gives us so we'll need to improve this per toolkit. It works very well for most cases though, that's why I might end up enabling it and work from there.

@person @antonok The alt text for the image says Onplus 6