Guido Günther @agx@librem.one

@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!

@debacle nice! In fact I like the extra window as I can just alt-tab back and forth when I need to look up something and as it follows thing-at-point it's already looked up when I get there . Completion based on gobject introspection would be cool sometimes for rarely used things.

MR is at https://gitlab.gnome.org/GNOME/devhelp/-/merge_requests/53

I somewhat revived #gnome's #devhelp --search-assistant for library documentation generated using gi-docgen (which thankfully more and more projects around #gtk switch to). This allows me to have quick doc access in #emacs again where I was only looking at an empty window before:

@rmader @awai @linmob Myself won't be at FOSDEM but that won't be a big loss in that regard as my camera knowledge is basically non existent. 😋

@tuxdevices Would be great to mention Pavel who was driving the bulk of this "more automated photo taking/video" work: https://source.puri.sm/Librem5/millipixels/-/merge_requests?scope=all&state=merged&author_username=pavel