[SailfishDevel] Flatpak for Sailfish

[szopin at gmail.com]

This is amazing, if there is something I can do to help please let me know, not being tied to os version of qt is awesome, we could maybe get a proper browser with this? Hope leszek is on the list 

On Friday, 27 December 2019, rinigus wrote:
> I have a breakthrough. Had to compile libhybris with
> 
> --with-default-hybris-ld-library-path=/usr/lib/arm-linux-gnueabihf/GL/default/libexec/droid-hybris/system/lib:/vendor/lib:/system/lib:/odm/lib
> 
> and enable "--filesystem=host --device=all" in "flatpak run". As a result,
> I have some Qt flatpak apps running. While Falkon does crash on init,
> qutebrowser
> started.
> 
> Few issues:
> 
> Keyboard:
> Enabling Qt Virtual Keyboard with QT_IM_MODULE=qtvirtualkeyboard makes it
> crash though, with a message
> 
> 19:48:20 WARNING: requestActivate() called for
>  QtVirtualKeyboard::InputView(0xe9150998)  which has
> Qt::WindowDoesNotAcceptFocus set.
> 
> and flashing virtual keyboard on screen for a moment. I guess, we will have
> to use
> QML InputPanel to make it work for now.
> 
> 
> Minimizing:
> When you minimize an application, you get the application minimized into
> small live icon and you get a message in terminal
> 
> 20:25:39 WARNING: Minimizing is not supported on wl-shell. Consider using
> xdg-shell instead.
> 20:25:39 WARNING: Wayland does not support QWindow::requestActivate()
> 
> You can restore application immediately from small representation of it.
> However, if you had lockscreen or some other app over it, the icon
> disappears and its impossible to get the window back. At the same time, the
> application keeps running. qxcompositor does help, as apps are not
> minimized when staying on Wayland screen over there.
> 
> So, to summarize:
> 
> 1. Flatpak applications can run on SFOS.
> 
> 2. We need to move away from wl-shell and get to the non-deprecated
> composer option (fixing minimizing and restoring applications). That will
> enable Gdk apps as well.
> 
> 3. Ideally, libhybris should allow to specify hybris-ld-library-path during
> runtime. Otherwise, we have to compile separate versions of hybris - one
> for device and one for flatpaks. On device, two copies are needed anyway
> (probably hardlinking will work as well).
> 
> 4. Keyboard will need some work. I presume that by moving to supported
> composer we could get around it with qt virtual keyboard. There is a
> workaround for our apps, if needed. For native look, if possible, someone
> will have to comment.
> 
> Looks like #2 is a breaker right now and I don't know if it is possible to
> fix anytime soon.
> 
> Cheers,
> 
> Rinigus
>

-- 
Sent from my Jolla