Guido Günther @agx@librem.one

@joshfowler I think the best thing is to have phosh running nested on your desktop and then use gtk-inspector to modify e.g. CSS at runtime. That's easier (and faster) than pocking at the phone directly.

@joshfowler I'm not familiar with the regulations in UK but there's https://gitlab.gnome.org/World/Phosh/phosh/-/merge_requests/904 - basically for the bits in calls to land.

@joshfowler Generally speaking: while we try to take higher resolution devices into account when developing phosh it's not continuously tested (e.g. phosh's CI tests 360x720) so it needs people to step up to send patches for those devices and to get rid of the papercuts (and we can then make sure we don't regress via CI).

@joshfowler Ah regarding lock screen, you want to send patches to allow for more spacing between the keys and maybe even scale up a bit.

Regarding switching keyboards:
That depends on your distro. In Debian it's just `update-alternatives`. On pmOS building from source and installing to `/usr/local/` should do the trick. That's at least how I run it there for testing. Note that phosh-osk-stub is experimental so make sure you have ssh access.

@joshfowler But lockscreen is fixed?

Your screenshot show's squeekboard so I assume you're hitting https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/338 . I'm using phosh-osk-stub instead as I rely on some of it's features and that ones scales according to the screenshot I posted.

@joshfowler hmm...seems my reply somehow vanished: pmOS tweaks sets CSS which likely causes your problem. Basically if you add additional CSS you got to keep the pieces.
There's some other caveats with fractinal scaling atm but phosh itself should render correctly at scale 2.5 (it does here on current main).

@joshfowler I assume you apply some custom CSS then? Both #phosh's lockscreen and #phosh-osk-stub look right here at scale 2.5 (got myself temporary access to a Oneplus 6T to check that)

I've tagged an initial version 0.0.1 of gmobile, a small supporting library used by #phosh, #feedbackd and soon #phoc for notches/cutouts, timers and the like: https://gitlab.gnome.org/guidog/gmobile/-/releases/v0.0.1

This is in early stages but maybe there's some stuff useful for other projects.

#linuxmobile #mobilelinux

@dos causality vs correlation strikes again.

As the last component of the 0.23.0 release set #phoc 0.23.0 is out, fixing the pixman renderer to help #CI testing, running in #qemu and platforms that can't or don't want to use GLES2. If you don't need any of these it's safe to wait for 0.24.0.

Release notes at: https://gitlab.gnome.org/World/Phosh/phoc/-/releases/v0.23.0

#phosh #wayland #wlroots #linuxonmobile #mobile #gnome #gnomeonmobile #librem5

@gnumdk I certainly appreciate any help to get the top panel flow around notches nicely once the groundwork landed (my #librem5 doesn't even need notches /cutout support). I hope we get some design input from @snwh how things could look like.

@hemish read thw whole thing: https://social.librem.one/@agx/109682949493890985

MRs are linked here: https://gitlab.gnome.org/guidog/gmobile/-/merge_requests/8

Next steps (after cleaning up a bit and getting it merged) is allowing phosh to make better use of that information (e.g. to shift ui elements to the side instead of down) and providing the information to wayland clients so e.g. video players can make use of it in fullscreen mode.

4️⃣ /4️⃣

phosh using that information to push the top panel down because there's a (simulated) notch:
3️⃣ /4️⃣

phoc rendering cutouts in nexted mode to simulate cutouts and rounded edges:

2️⃣ /4️⃣

Some progress to handle notches / cutouts of #linuxmobile phones better in #phosh : I have a small lib that gets panel cutout / notch information as #svg paths and can calculate a bounding box . #phoc can use it to render cutouts for debugging and #phosh can use it for layout (so far only to shift the panel down). (see follow up posts for more pictures).
1️⃣ /4️⃣

And as a late arrival there's phosh-tour 0.23.0 (https://gitlab.gnome.org/guidog/phosh-tour/-/releases/v0.23.0) mostly to fix metainfo validation.

@mykhaylo @debacle I''m kind of hooked to devhelp docs that ship in #debian as that makes sure the docs match exactly the version I'm developing against. Might become handy for other docs though. Thanks for the pointer!