@julianfairfax @deedend @devrtz @purism Both webkit (used in epiphany / GNOME Web) and chromium engines target mobile so while I prefer native apps too we shouldn't overlook that years of optimization for mobile went into these browser engines so they can run efficiently on phones. So I'd not dismiss webapps so easily.
@julianfairfax @deedend @devrtz @purism hydrogen works well for matrix and resource usage is o.k. in chromium. I've heard similar things for signal.
Also "neither are ready" needs references on what's missing - it depends on usage pattern. Native apps like flare or chatty are making good progress. Also if it's not an option for you it might be an option for others.
It also depends on how important a switch is for someone (I myself just can't imagine running around with an Android phone).
Only downside is that the keyboard doesn't unfold itself due to the lack of text-input-unstable-v3 in chromium but unfolding via button works.
2️⃣ /2️⃣
@wandy_dev Regarding webapps: Have you tried chromium? I usually:
- use the "Install <site>…" from within chromium
- Add "--enable-features=UseOzonePlatform --ozone-platform=wayland" to the desktop file in .local/share/applications
- launch the webapp and (if needed) open phosh-mobile-settings to "enable scale to fit" for this particular webapp
Although setup is cumbersome it
it gives me good performance.
1️⃣ /2️⃣
Guido Günther
boosted
A reminder that these little tools make designing for GNOME a little more pleasant.
Guido Günther
boosted
Guido Günther
boosted
@linmob @s31bz @bradlinder Yeah, the #librem5 is the one phone that most mobian developers currently recommend and use. Both purism and mobian devs are quite active with migrating things into @debian proper. We are aware of the price tag, but would like to reiterate that this actually includes salaries for mobile Linux developers.
Guido Günther
boosted
Oh, 2023 XDC schedule is available with a super colorful day of talks ❤️🧡💛💚💙💜🤎🖤🤍
[🌈+🎮]
"The Rainbow Treasure Map: advanced color management on Linux with AMD/Steam Deck" by Melissa Wen
[🌈+🐸+🎮]
"Rainbow Frogs: HDR + Color Management in Gamescope/SteamOS" by Joshua Ashton
+ KMS API color management workshop
This year conference is happening 17-19 Oct 2023 in Coruña, Spain - organized by @igalia
See 2023 XDC schedule at:
https://indico.freedesktop.org/event/4/timetable/#all.detailed
@deedend @devrtz @purism I encourage everyone to try PureOS on the Librem 5 to judge daily usability of the Librem 5 and if it's "the time yet".
One shouldn't draw that conclusion by looking at other devices (running other distros).
A single missing one line line patch or broken driver can considerably mess up daily usability.
@Dragon @junocomputers I thinks it's fine to charge for the fact that you need to make adaptions to run Linux fine. It's also fine to charge because you offer product support (including the software you put on it).
I really like to see well supported Linux first devices, that's why I think it's important to get this right. Otherwise we'll stay stuck in the "only for geeks" corner.
@katemason @junocomputers Not in the communities I'm aware of. But even when you do contribute upstream you should have product support and not expect the upstream projects to handle that for you.
Note that other on screen keyboards handle that well since a long time and that this really only affects the fallback to virtual-keyboard mode.
GTK apps using text-input-unstable-v3 don't care as they handle unicode via text-input so they worked well before and can even benefit from text completion.
2️⃣ /2️⃣
When splitting phosh-osk-stub out of #phosh one of my goals was "use it from day one". This required to hack in a virtual-keyboard driver so Electron apps (and other apps that can't deal with text-input-unstable-v3) can fall back to "emulated key presses" instead of using an input-method.
Prompted by input from Kai Lüke who (rightly) pointed out that the German layout was missing symbols in virtual-keyboard mode I revisited the situation and we can now handle more languages:
1️⃣ /2️⃣
@droidian Makes sense. We currently don't have anything planned that would make phosh require a newer phoc so the 0.32.0 cycle should at least be safe.
@janvlug @subins2000 @arunmani See "Setup" and "Configuration" at https://gitlab.gnome.org/guidog/phosh-osk-stub/-/blob/main/doc/phosh-osk-stub.rst
@droidian Congratulations! I noticed you didn't update phoc. Is there an issue with switching to newer wlroots or just: we didn't get around to it? For the moment this shouldn't be a problem on phones.
@Breakfastisready @subins2000 @arunmani Great. With https://gitlab.gnome.org/guidog/phosh-osk-stub/-/merge_requests/97 we can switch completion languages so it might be a good point in time to make sure your distribution ships govarnam and it's schema files 😄
@junocomputers
You get a completely free operating system, please support us in developing it with detailed
reports rather than pushing end user support upstream.
At the very minimum check with the communities upfront how to best interact and supply them with hardware.
2️⃣ /2️⃣
