@martijnbraam Sorry to read your frustration but *thank* *you* for your work on megapixels! I agree that it would be very good for the camera ecosystem to have another (maybe simpler) maintained implementation besides libcamera that can drive the hw we have.
We also have e.g. ffmpeg and gstreamer on the output decoding side and it's very useful to have both around.
1. Two people are trying to get Varnam running in Windows
2: Another trying to improve the library
3: Another from other side of the world trying to run it for Mobile Linux
4: Another trying to plug Varnam in a big site
5: and more...
Thank you contributors <3. Peak Varnam dev
If you're using that and want to run phosh against it make sure to pick up phosh's main branch. For phog use https://gitlab.com/mobian1/phog/-/merge_requests/7
We're tracking wlroot's git on #phoc's main branch now: https://gitlab.gnome.org/World/Phosh/phoc/-/merge_requests/463 .
@mxmehl @openrail Glad to hear that! Any timeframe when end user facing apps like navigator will become open source? This would allow people to avoid proprietary app stores and to learn how to implement advanced features for other platforms like #LinuxMobile / #Phosh without guessing.
Related article: https://mobilsicher.de/hintergrund/der-db-ist-es-egal-dass-menschen-ihre-app-nur-mit-google-oder-apple-nutzen-koennen
@000exploit I assume you mean text selection via touch input: That is mostly handled by the toolkit (e.g. gtk). There can be compositor bugs too but I'd start looking at the toolkit side first.
@joeyh The format still works great, it's super handy to have the entire history of security issues within a single Emacs buffer,especially when cross correlating with older issues
phosh 0.33.0 is out 🚀📱:
Allows to toggle password visibility on/off in all modal dialogs, new
🔒-screen plugin to launch tasks, improved support for Indic languages ➕ UI and troubleshooting tab improvements in mobile settings.
Check out the full release notes at https://phosh.mobi/releases/rel-0.33.0/
#phosh #librem5 #gnome #linux #mobile #LinuxMobile #MobileLinux #gnomemobile
NEW POST: It's now been a year since The Muskover, what does my use of social media look like now, both as a reader and a writer?
Thanks to the stellar work of Arjan Molenaar, the pygobject bindings have been dramatically improving over the past month. Now Python developers can finally use instances of fundamental types, which was one of the big blockers for people implementing custom widgets with GTK4.
Starting with the GNOME 46 run time, you'll be able to do advanced custom drawing using render nodes, as well as accessing low level windowing system event objects.
@linmob Enjoy vacation!
We hit bug number #1000 in #phosh: https://gitlab.gnome.org/World/Phosh/phosh/-/issues/1000
(and it's surprisingly not phone related)
@devrtz @postmarketOS @kop316 @mobian @awai
Rock on pmOS and Mobian and thanks a lot for the shout-out 😍
@FineFindus did you check ~/.var/app and ~/.local/share/flatpak ? It even puts more stuff in $HOME over here 😄
I ever so often close the 🎵- player and when grabbing the 📱 I'd have to unlock it to just start the 🎵 player and then 🔒 the 📱 right away again (as there's #mpris controls on the 🔒-screen then anyway).
Hence I wrote a small #phosh plugin to add arbitrary "launchers" to the 🔒-screen via a desktop file.
This is very simplistic atm (as we e.g. don't track app-state) but gets the job done initially.
I only used it for that purpose but there's other potential use cases:
Interesting talk by Michael Tretter at #xdc2023 about Wayland shells on embedded systems: https://www.youtube.com/watch?v=qK2Emqp9t0g&t=14240s
@arunmani for Debian I'd put phoc / wlroots git snapshots into experimental. Distros would likely ship phoc versions based on stable wlroots anyway. We can then work from there with wlroots upstream on releases hopefully sharing some of the load.
@awai Having a phosh and phoc version that runs against latest wlroots (or latest set of libraries in particular) certainly makes things a lot easier (and helps us to e.g. transition away from deprecated protocols and APIs sooner, etc). We accumulated quiet a bit of cruft since not doing that anymore (which is mostly cleaned up now but I don't want to do it again 😄 )