Re: [SailfishDevel] Flatpak for Sailfish

2020-01-05 Thread rinigus
Morning!

Re compositor issue: that has been worked around by having
compositor-in-compositor. In theory, but I didn't look too much more than a
day into it, we could have headless compositor rendered on gles widget
which could be rather current, with all protocols supported. I mainly
bailed out to keep this project feasible and getting somewhere in
reasonable amount of time.

Re keyboard: current solution is to incorporate keyboard into the app by
adding into main window. I am waiting for Sailfish keyboard gurus to
comment on it with the hope that we can use some kind of plugin in flatpaks
for communication with SFOS keyboards (dbus is available, for example).

Rinigus

On Mon, Jan 6, 2020 at 7:55 AM Alexander Akulich 
wrote:

> Hi all and thank you for working on this.
>
> Back in 2018 I had Qt 5.9 and Qt 5.11 builds for SFOS (they are not
> available anymore because of changes in OBS repos), but the builds
> were not usable because the of the same issues — wayland and virtual
> keyboard. As far as I understood, a compositor with newer wayland
> protocol is needed to support minimize and switching back to full
> screen (the applications were able to start, but I couldn't open them
> again after minimize).
>
> On Sat, Dec 28, 2019 at 3:54 AM Damien Caliste  wrote:
> >
> > Thank you Rinigus for all of this. Indeed, the current main blocker
> seems to be the fact that xdg-shell is not available in Lipstick. This is
> linked to the ancient version of QtWayland, even not 5.6, but still 5.4 !
> They already have a 5.9 branch in SailfishOS git (
> https://git.sailfishos.org/mer-core/qtwayland/tree/mer-5.9), but we need
> to wait for Jolla to make the Qt switch. I don't think it's something
> community can change on device... I hope I can be proven wrong though.
> >
> > Damien.
> > ___
> > SailfishOS.org Devel mailing list
> > To unsubscribe, please send a mail to
> devel-unsubscr...@lists.sailfishos.org
> ___
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to
> devel-unsubscr...@lists.sailfishos.org
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Flatpak for Sailfish

2020-01-05 Thread Alexander Akulich
Hi all and thank you for working on this.

Back in 2018 I had Qt 5.9 and Qt 5.11 builds for SFOS (they are not
available anymore because of changes in OBS repos), but the builds
were not usable because the of the same issues — wayland and virtual
keyboard. As far as I understood, a compositor with newer wayland
protocol is needed to support minimize and switching back to full
screen (the applications were able to start, but I couldn't open them
again after minimize).

On Sat, Dec 28, 2019 at 3:54 AM Damien Caliste  wrote:
>
> Thank you Rinigus for all of this. Indeed, the current main blocker seems to 
> be the fact that xdg-shell is not available in Lipstick. This is linked to 
> the ancient version of QtWayland, even not 5.6, but still 5.4 ! They already 
> have a 5.9 branch in SailfishOS git 
> (https://git.sailfishos.org/mer-core/qtwayland/tree/mer-5.9), but we need to 
> wait for Jolla to make the Qt switch. I don't think it's something community 
> can change on device... I hope I can be proven wrong though.
>
> Damien.
> ___
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] symbol lookup error from syncemail-client (undefined symbol: _ZN5Buteo13PluginManagerC1Ev)

2020-01-05 Thread deloptes
Slava Monich wrote:

> _ZN5Buteo13PluginManagerC1Ev is Buteo::PluginManager::PluginManager()
> 
> 
> $ c++filt _ZN5Buteo13PluginManagerC1Ev
> Buteo::PluginManager::PluginManager()
> 
> There's no such thing:
> 
> 
>
https://git.sailfishos.org/deloptes/buteo-syncfw/blob/master/libbuteosyncfw/pluginmgr/PluginManager.h#L96
> 
> These are available constructors:
> 
> $ nm -D /usr/lib/libbuteosyncfw5.so.0 | grep ZN5Buteo13PluginManagerC
> 0003f0b8 T _ZN5Buteo13PluginManagerC1ERK7QString
> 0003f0b8 T _ZN5Buteo13PluginManagerC2ERK7QString
> 
> $ c++filt _ZN5Buteo13PluginManagerC1ERK7QString
> Buteo::PluginManager::PluginManager(QString const&)
> 
> Something must be wrong with your build environment, e.g. you're pulling
> in wrong headers from somewhere.
> 
> Cheers,
> -Slava

I described the problem here:
https://together.jolla.com/question/220678/syncemail-client-undefined-symbol-_zn5buteo13pluginmanagerc1ev/

I don't understand what you mean b y pulling wrong headers - the constructor
is: Buteo::PluginManager::PluginManager(QString const&)

All the Jolla plugins use a constructor without argument. The 3 with
argument are from what I've compiled locally. I have not seen it with
3.2.0.12

Can you or someone check on your side pls?

# ls -1 /usr/lib/buteo-plugins-qt5/oopp/* | while read line; do echo $line; 
nm -CD $line | grep 'Buteo::PluginManager::PluginManager'; done
/usr/lib/buteo-plugins-qt5/oopp/caldav-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/carddav-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/dropbox-backup-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/dropbox-images-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/facebook-calendars-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/facebook-contacts-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/facebook-images-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/facebook-signon-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/google-calendars-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/google-contacts-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/google-signon-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/onedrive-backup-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/onedrive-images-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/onedrive-signon-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/sailfisheas-calendars-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/sailfisheas-contacts-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/sailfisheas-email-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/sociald-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/syncemail-client
 U Buteo::PluginManager::PluginManager(QString const&)
/usr/lib/buteo-plugins-qt5/oopp/syncml-client
 U Buteo::PluginManager::PluginManager(QString const&)
/usr/lib/buteo-plugins-qt5/oopp/syncml-server
 U Buteo::PluginManager::PluginManager(QString const&)
/usr/lib/buteo-plugins-qt5/oopp/twitter-notifications-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/twitter-posts-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/vk-calendars-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/vk-contacts-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/vk-images-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/vk-notifications-client
 U Buteo::PluginManager::PluginManager()
/usr/lib/buteo-plugins-qt5/oopp/vk-posts-client
 U Buteo::PluginManager::PluginManager()


___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Flatpak for Sailfish

2020-01-05 Thread rinigus
Good part is that this home-cooked libhybris will live separately from the
main one in your home folder (see
https://github.com/sailfishos-flatpak/flatpak-runner/blob/master/scripts/flatpak-extension-hybris
for script generating it). So, you can experiment while keeping system one
intact.

Rinigus

On Mon, Jan 6, 2020 at 12:10 AM  wrote:

> I'm probably totally wrong, but you can run all kinds of homecooked
> libhybris versions on a device without needing kernel recompiled, unless
> some specific kernel options are missing?
>
> On Sunday, 5 January 2020, rinigus wrote:
> > Re kernel options: USER_NS is one of them, rest I am not sure as it
> worked
> > immediately for me on Xperia XZ2. As a result, I never looked too deeply
> > into it.
> >
> > Re libhybris: isn't it compiled against device specific droid-hal?
> >
> > Rinigus
> >
> > On Sun, Jan 5, 2020 at 11:37 PM  wrote:
> >
> > > If it's only in libhybris, then it's not device specific? Which exactly
> > > kernel options need to be turned on for it? Or I'm totally confused
> > >
> > > On Sunday, 5 January 2020, rinigus wrote:
> > > > Hi,
> > > >
> > > > I think that the patch suggested for libhybris is a bugfix. So, I
> hope it
> > > > will be merged and distributed with one of the next SFOS updates.
> > > Assuming
> > > > that Jolla C is still getting updates, you should get it too.
> > > >
> > > > Now, libhybris bug is in the linker, as you can see from my PR. I
> don't
> > > > know how device-specific it is, hopefully knowledgeable porters can
> chip
> > > in
> > > > and comment on it. If its not device specific then we can just
> package
> > > the
> > > > linker and use the rest as it is on device.
> > > >
> > > > Let's see what the next few days bring. I presume many of developers
> are
> > > > back from holidays next week which could speed up the response.
> > > >
> > > > Cheers,
> > > >
> > > > Rinigus
> > > >
> > > >
> > > >
> > > > On Sun, Jan 5, 2020 at 10:52 PM  wrote:
> > > >
> > > > > It's device specific? Shame, doubt jolla C can help then. Still
> hopeful
> > > > > the eventual cosmo communicator edition will support it. Any hints
> what
> > > > > needs to be enabled in kernel?
> > > > >
> > > > > Thanks in advance,
> > > > > szopin
> > > > >
> > > > > On Sunday, 5 January 2020, rinigus wrote:
> > > > > > Hi,
> > > > > >
> > > > > > I have moved all repositories required for Flatpak support to
> > > > > > https://github.com/sailfishos-flatpak . Documentation is
> available
> > > at
> > > > > > https://github.com/sailfishos-flatpak/main describing how to
> > > install and
> > > > > > develop using this environment. Issues are expected to be filed
> fixed
> > > > > under
> > > > > > https://github.com/sailfishos-flatpak/main and, when
> appropriate,
> > > under
> > > > > > https://github.com/sailfishos-flatpak/flatpak-runner. I tried to
> > > list
> > > > > all
> > > > > > current issues under those repositories.
> > > > > >
> > > > > > I have also opened a thread at TMO (
> > > > > > http://talk.maemo.org/showthread.php?p=1564143) for those who
> prefer
> > > > > that
> > > > > > way of communication.
> > > > > >
> > > > > > Cheers,
> > > > > >
> > > > > > Rinigus
> > > > > >
> > > > > > On Sat, Jan 4, 2020 at 10:22 AM rinigus 
> > > wrote:
> > > > > >
> > > > > > > Excellent! If something in kernel config is missing, I expect
> that
> > > you
> > > > > > > could use Xperia 10 as a base to check the settings or for
> Xperia
> > > XZ2
> > > > > used
> > > > > > > by me at
> > > > > > >
> > > > >
> > >
> https://github.com/sailfishos-sony-tama/android_kernel_sony_msm/blob/hybris-sony-aosp-9.0.0-4.9-tama-sony/arch/arm64/configs/aosp_tama_akari_defconfig
> > > > > > >
> > > > > > > Rinigus
> > > > > > >
> > > > > > > On Sat, Jan 4, 2020 at 12:47 AM Adam Pigg 
> > > wrote:
> > > > > > >
> > > > > > >> Ill build it on mido and try it out, thanks!
> > > > > > >>
> > > > > > >> On Fri, 3 Jan 2020 at 22:45, rinigus 
> > > wrote:
> > > > > > >>
> > > > > > >>> Hi,
> > > > > > >>>
> > > > > > >>> I have submitted PR to libhybris allowing to use Flatpak on
> > > hybris
> > > > > > >>> devices with the same version serving its main purpose and
> inside
> > > > > Flatpak
> > > > > > >>> sandbox: https://github.com/libhybris/libhybris/pull/433.
> > > > > > >>>
> > > > > > >>> As soon as your device has such libhybris, you could
> > > > > > >>>
> > > > > > >>> - use
> > > https://build.merproject.org/project/show/home:rinigus:flatpak
> > > > > to
> > > > > > >>> install flatpak, flatpak-runner
> > > > > > >>> - run flatpak-extension-hybris to generate Flatpah hybris
> > > extension
> > > > > at
> > > > > > >>> user nemo's home (run as nemo)
> > > > > > >>> - install flatpak apps, see instructions at Flathub on how
> to do
> > > it
> > > > > > >>> - run them using flatpak-runner
> > > > > > >>>
> > > > > > >>> Many things don't work, but would be faster to get it fixed
> > > together
> > > > > > >>> with other devs.
> > > > > > >>>
> > > > > > >>> Cheers.

Re: [SailfishDevel] Flatpak for Sailfish

2020-01-05 Thread szopin
I'm probably totally wrong, but you can run all kinds of homecooked libhybris 
versions on a device without needing kernel recompiled, unless some specific 
kernel options are missing?

On Sunday, 5 January 2020, rinigus wrote:
> Re kernel options: USER_NS is one of them, rest I am not sure as it worked
> immediately for me on Xperia XZ2. As a result, I never looked too deeply
> into it.
> 
> Re libhybris: isn't it compiled against device specific droid-hal?
> 
> Rinigus
> 
> On Sun, Jan 5, 2020 at 11:37 PM  wrote:
> 
> > If it's only in libhybris, then it's not device specific? Which exactly
> > kernel options need to be turned on for it? Or I'm totally confused
> >
> > On Sunday, 5 January 2020, rinigus wrote:
> > > Hi,
> > >
> > > I think that the patch suggested for libhybris is a bugfix. So, I hope it
> > > will be merged and distributed with one of the next SFOS updates.
> > Assuming
> > > that Jolla C is still getting updates, you should get it too.
> > >
> > > Now, libhybris bug is in the linker, as you can see from my PR. I don't
> > > know how device-specific it is, hopefully knowledgeable porters can chip
> > in
> > > and comment on it. If its not device specific then we can just package
> > the
> > > linker and use the rest as it is on device.
> > >
> > > Let's see what the next few days bring. I presume many of developers are
> > > back from holidays next week which could speed up the response.
> > >
> > > Cheers,
> > >
> > > Rinigus
> > >
> > >
> > >
> > > On Sun, Jan 5, 2020 at 10:52 PM  wrote:
> > >
> > > > It's device specific? Shame, doubt jolla C can help then. Still hopeful
> > > > the eventual cosmo communicator edition will support it. Any hints what
> > > > needs to be enabled in kernel?
> > > >
> > > > Thanks in advance,
> > > > szopin
> > > >
> > > > On Sunday, 5 January 2020, rinigus wrote:
> > > > > Hi,
> > > > >
> > > > > I have moved all repositories required for Flatpak support to
> > > > > https://github.com/sailfishos-flatpak . Documentation is available
> > at
> > > > > https://github.com/sailfishos-flatpak/main describing how to
> > install and
> > > > > develop using this environment. Issues are expected to be filed fixed
> > > > under
> > > > > https://github.com/sailfishos-flatpak/main and, when appropriate,
> > under
> > > > > https://github.com/sailfishos-flatpak/flatpak-runner. I tried to
> > list
> > > > all
> > > > > current issues under those repositories.
> > > > >
> > > > > I have also opened a thread at TMO (
> > > > > http://talk.maemo.org/showthread.php?p=1564143) for those who prefer
> > > > that
> > > > > way of communication.
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Rinigus
> > > > >
> > > > > On Sat, Jan 4, 2020 at 10:22 AM rinigus 
> > wrote:
> > > > >
> > > > > > Excellent! If something in kernel config is missing, I expect that
> > you
> > > > > > could use Xperia 10 as a base to check the settings or for Xperia
> > XZ2
> > > > used
> > > > > > by me at
> > > > > >
> > > >
> > https://github.com/sailfishos-sony-tama/android_kernel_sony_msm/blob/hybris-sony-aosp-9.0.0-4.9-tama-sony/arch/arm64/configs/aosp_tama_akari_defconfig
> > > > > >
> > > > > > Rinigus
> > > > > >
> > > > > > On Sat, Jan 4, 2020 at 12:47 AM Adam Pigg 
> > wrote:
> > > > > >
> > > > > >> Ill build it on mido and try it out, thanks!
> > > > > >>
> > > > > >> On Fri, 3 Jan 2020 at 22:45, rinigus 
> > wrote:
> > > > > >>
> > > > > >>> Hi,
> > > > > >>>
> > > > > >>> I have submitted PR to libhybris allowing to use Flatpak on
> > hybris
> > > > > >>> devices with the same version serving its main purpose and inside
> > > > Flatpak
> > > > > >>> sandbox: https://github.com/libhybris/libhybris/pull/433.
> > > > > >>>
> > > > > >>> As soon as your device has such libhybris, you could
> > > > > >>>
> > > > > >>> - use
> > https://build.merproject.org/project/show/home:rinigus:flatpak
> > > > to
> > > > > >>> install flatpak, flatpak-runner
> > > > > >>> - run flatpak-extension-hybris to generate Flatpah hybris
> > extension
> > > > at
> > > > > >>> user nemo's home (run as nemo)
> > > > > >>> - install flatpak apps, see instructions at Flathub on how to do
> > it
> > > > > >>> - run them using flatpak-runner
> > > > > >>>
> > > > > >>> Many things don't work, but would be faster to get it fixed
> > together
> > > > > >>> with other devs.
> > > > > >>>
> > > > > >>> Cheers.
> > > > > >>>
> > > > > >>> Rinigus
> > > > > >>>
> > > > > >>> On Fri, Jan 3, 2020 at 12:18 AM rinigus 
> > > > wrote:
> > > > > >>>
> > > > >  Hi,
> > > > > 
> > > > >  just finished the first version of a wrapper for 'flatpak run'
> > > > command
> > > > >  as well, available at https://github.com/rinigus/flatpak-runner
> > .
> > > > Its
> > > > >  based on qxcompositor and it opens new Wayland server before
> > > > running an
> > > > >  application, all explained in README. Device rotation is
> > supported
> > > > and
> > > > >  should be followed.
> > > > > 
> > > > >  So, 

Re: [SailfishDevel] Flatpak for Sailfish

2020-01-05 Thread rinigus
Re kernel options: USER_NS is one of them, rest I am not sure as it worked
immediately for me on Xperia XZ2. As a result, I never looked too deeply
into it.

Re libhybris: isn't it compiled against device specific droid-hal?

Rinigus

On Sun, Jan 5, 2020 at 11:37 PM  wrote:

> If it's only in libhybris, then it's not device specific? Which exactly
> kernel options need to be turned on for it? Or I'm totally confused
>
> On Sunday, 5 January 2020, rinigus wrote:
> > Hi,
> >
> > I think that the patch suggested for libhybris is a bugfix. So, I hope it
> > will be merged and distributed with one of the next SFOS updates.
> Assuming
> > that Jolla C is still getting updates, you should get it too.
> >
> > Now, libhybris bug is in the linker, as you can see from my PR. I don't
> > know how device-specific it is, hopefully knowledgeable porters can chip
> in
> > and comment on it. If its not device specific then we can just package
> the
> > linker and use the rest as it is on device.
> >
> > Let's see what the next few days bring. I presume many of developers are
> > back from holidays next week which could speed up the response.
> >
> > Cheers,
> >
> > Rinigus
> >
> >
> >
> > On Sun, Jan 5, 2020 at 10:52 PM  wrote:
> >
> > > It's device specific? Shame, doubt jolla C can help then. Still hopeful
> > > the eventual cosmo communicator edition will support it. Any hints what
> > > needs to be enabled in kernel?
> > >
> > > Thanks in advance,
> > > szopin
> > >
> > > On Sunday, 5 January 2020, rinigus wrote:
> > > > Hi,
> > > >
> > > > I have moved all repositories required for Flatpak support to
> > > > https://github.com/sailfishos-flatpak . Documentation is available
> at
> > > > https://github.com/sailfishos-flatpak/main describing how to
> install and
> > > > develop using this environment. Issues are expected to be filed fixed
> > > under
> > > > https://github.com/sailfishos-flatpak/main and, when appropriate,
> under
> > > > https://github.com/sailfishos-flatpak/flatpak-runner. I tried to
> list
> > > all
> > > > current issues under those repositories.
> > > >
> > > > I have also opened a thread at TMO (
> > > > http://talk.maemo.org/showthread.php?p=1564143) for those who prefer
> > > that
> > > > way of communication.
> > > >
> > > > Cheers,
> > > >
> > > > Rinigus
> > > >
> > > > On Sat, Jan 4, 2020 at 10:22 AM rinigus 
> wrote:
> > > >
> > > > > Excellent! If something in kernel config is missing, I expect that
> you
> > > > > could use Xperia 10 as a base to check the settings or for Xperia
> XZ2
> > > used
> > > > > by me at
> > > > >
> > >
> https://github.com/sailfishos-sony-tama/android_kernel_sony_msm/blob/hybris-sony-aosp-9.0.0-4.9-tama-sony/arch/arm64/configs/aosp_tama_akari_defconfig
> > > > >
> > > > > Rinigus
> > > > >
> > > > > On Sat, Jan 4, 2020 at 12:47 AM Adam Pigg 
> wrote:
> > > > >
> > > > >> Ill build it on mido and try it out, thanks!
> > > > >>
> > > > >> On Fri, 3 Jan 2020 at 22:45, rinigus 
> wrote:
> > > > >>
> > > > >>> Hi,
> > > > >>>
> > > > >>> I have submitted PR to libhybris allowing to use Flatpak on
> hybris
> > > > >>> devices with the same version serving its main purpose and inside
> > > Flatpak
> > > > >>> sandbox: https://github.com/libhybris/libhybris/pull/433.
> > > > >>>
> > > > >>> As soon as your device has such libhybris, you could
> > > > >>>
> > > > >>> - use
> https://build.merproject.org/project/show/home:rinigus:flatpak
> > > to
> > > > >>> install flatpak, flatpak-runner
> > > > >>> - run flatpak-extension-hybris to generate Flatpah hybris
> extension
> > > at
> > > > >>> user nemo's home (run as nemo)
> > > > >>> - install flatpak apps, see instructions at Flathub on how to do
> it
> > > > >>> - run them using flatpak-runner
> > > > >>>
> > > > >>> Many things don't work, but would be faster to get it fixed
> together
> > > > >>> with other devs.
> > > > >>>
> > > > >>> Cheers.
> > > > >>>
> > > > >>> Rinigus
> > > > >>>
> > > > >>> On Fri, Jan 3, 2020 at 12:18 AM rinigus 
> > > wrote:
> > > > >>>
> > > >  Hi,
> > > > 
> > > >  just finished the first version of a wrapper for 'flatpak run'
> > > command
> > > >  as well, available at https://github.com/rinigus/flatpak-runner
> .
> > > Its
> > > >  based on qxcompositor and it opens new Wayland server before
> > > running an
> > > >  application, all explained in README. Device rotation is
> supported
> > > and
> > > >  should be followed.
> > > > 
> > > >  So, as it is:
> > > > 
> > > >  - we have to resolve libhybris linker issue to make it possible
> to
> > > >  distribute.
> > > >  - keyboard is not supported currently. At present, app has to
> have
> > > >  qtvirtualkeyboard support added as in
> > > > 
> > >
> https://doc.qt.io/qt-5/qtvirtualkeyboard-deployment-guide.html#creating-inputpanel
> > > >  .
> > > >  - only single-window apps are working well, such as QML
> developed
> > > for
> > > >  mobile
> > > >  - no 

Re: [SailfishDevel] Flatpak for Sailfish

2020-01-05 Thread szopin
If it's only in libhybris, then it's not device specific? Which exactly kernel 
options need to be turned on for it? Or I'm totally confused

On Sunday, 5 January 2020, rinigus wrote:
> Hi,
> 
> I think that the patch suggested for libhybris is a bugfix. So, I hope it
> will be merged and distributed with one of the next SFOS updates. Assuming
> that Jolla C is still getting updates, you should get it too.
> 
> Now, libhybris bug is in the linker, as you can see from my PR. I don't
> know how device-specific it is, hopefully knowledgeable porters can chip in
> and comment on it. If its not device specific then we can just package the
> linker and use the rest as it is on device.
> 
> Let's see what the next few days bring. I presume many of developers are
> back from holidays next week which could speed up the response.
> 
> Cheers,
> 
> Rinigus
> 
> 
> 
> On Sun, Jan 5, 2020 at 10:52 PM  wrote:
> 
> > It's device specific? Shame, doubt jolla C can help then. Still hopeful
> > the eventual cosmo communicator edition will support it. Any hints what
> > needs to be enabled in kernel?
> >
> > Thanks in advance,
> > szopin
> >
> > On Sunday, 5 January 2020, rinigus wrote:
> > > Hi,
> > >
> > > I have moved all repositories required for Flatpak support to
> > > https://github.com/sailfishos-flatpak . Documentation is available at
> > > https://github.com/sailfishos-flatpak/main describing how to install and
> > > develop using this environment. Issues are expected to be filed fixed
> > under
> > > https://github.com/sailfishos-flatpak/main and, when appropriate, under
> > > https://github.com/sailfishos-flatpak/flatpak-runner. I tried to list
> > all
> > > current issues under those repositories.
> > >
> > > I have also opened a thread at TMO (
> > > http://talk.maemo.org/showthread.php?p=1564143) for those who prefer
> > that
> > > way of communication.
> > >
> > > Cheers,
> > >
> > > Rinigus
> > >
> > > On Sat, Jan 4, 2020 at 10:22 AM rinigus  wrote:
> > >
> > > > Excellent! If something in kernel config is missing, I expect that you
> > > > could use Xperia 10 as a base to check the settings or for Xperia XZ2
> > used
> > > > by me at
> > > >
> > https://github.com/sailfishos-sony-tama/android_kernel_sony_msm/blob/hybris-sony-aosp-9.0.0-4.9-tama-sony/arch/arm64/configs/aosp_tama_akari_defconfig
> > > >
> > > > Rinigus
> > > >
> > > > On Sat, Jan 4, 2020 at 12:47 AM Adam Pigg  wrote:
> > > >
> > > >> Ill build it on mido and try it out, thanks!
> > > >>
> > > >> On Fri, 3 Jan 2020 at 22:45, rinigus  wrote:
> > > >>
> > > >>> Hi,
> > > >>>
> > > >>> I have submitted PR to libhybris allowing to use Flatpak on hybris
> > > >>> devices with the same version serving its main purpose and inside
> > Flatpak
> > > >>> sandbox: https://github.com/libhybris/libhybris/pull/433.
> > > >>>
> > > >>> As soon as your device has such libhybris, you could
> > > >>>
> > > >>> - use https://build.merproject.org/project/show/home:rinigus:flatpak
> > to
> > > >>> install flatpak, flatpak-runner
> > > >>> - run flatpak-extension-hybris to generate Flatpah hybris extension
> > at
> > > >>> user nemo's home (run as nemo)
> > > >>> - install flatpak apps, see instructions at Flathub on how to do it
> > > >>> - run them using flatpak-runner
> > > >>>
> > > >>> Many things don't work, but would be faster to get it fixed together
> > > >>> with other devs.
> > > >>>
> > > >>> Cheers.
> > > >>>
> > > >>> Rinigus
> > > >>>
> > > >>> On Fri, Jan 3, 2020 at 12:18 AM rinigus 
> > wrote:
> > > >>>
> > >  Hi,
> > > 
> > >  just finished the first version of a wrapper for 'flatpak run'
> > command
> > >  as well, available at https://github.com/rinigus/flatpak-runner .
> > Its
> > >  based on qxcompositor and it opens new Wayland server before
> > running an
> > >  application, all explained in README. Device rotation is supported
> > and
> > >  should be followed.
> > > 
> > >  So, as it is:
> > > 
> > >  - we have to resolve libhybris linker issue to make it possible to
> > >  distribute.
> > >  - keyboard is not supported currently. At present, app has to have
> > >  qtvirtualkeyboard support added as in
> > > 
> > https://doc.qt.io/qt-5/qtvirtualkeyboard-deployment-guide.html#creating-inputpanel
> > >  .
> > >  - only single-window apps are working well, such as QML developed
> > for
> > >  mobile
> > >  - no sound so far
> > >  - probably many other things are missing, haven't bumped into them.
> > > 
> > >  Essentially, we will have access to the latest Qt, but would have to
> > >  write apps for this use. Fortunately, it all goes along SFOS
> > programming
> > >  and should be simple to convert later to Silica, when/if it catches
> > up with
> > >  Qt versions.
> > > 
> > >  I guess we can get better integration after it will be simple to
> > >  install on other devices and start using it by others.
> > > 
> > >  

Re: [SailfishDevel] Flatpak for Sailfish

2020-01-05 Thread rinigus
Hi,

I think that the patch suggested for libhybris is a bugfix. So, I hope it
will be merged and distributed with one of the next SFOS updates. Assuming
that Jolla C is still getting updates, you should get it too.

Now, libhybris bug is in the linker, as you can see from my PR. I don't
know how device-specific it is, hopefully knowledgeable porters can chip in
and comment on it. If its not device specific then we can just package the
linker and use the rest as it is on device.

Let's see what the next few days bring. I presume many of developers are
back from holidays next week which could speed up the response.

Cheers,

Rinigus



On Sun, Jan 5, 2020 at 10:52 PM  wrote:

> It's device specific? Shame, doubt jolla C can help then. Still hopeful
> the eventual cosmo communicator edition will support it. Any hints what
> needs to be enabled in kernel?
>
> Thanks in advance,
> szopin
>
> On Sunday, 5 January 2020, rinigus wrote:
> > Hi,
> >
> > I have moved all repositories required for Flatpak support to
> > https://github.com/sailfishos-flatpak . Documentation is available at
> > https://github.com/sailfishos-flatpak/main describing how to install and
> > develop using this environment. Issues are expected to be filed fixed
> under
> > https://github.com/sailfishos-flatpak/main and, when appropriate, under
> > https://github.com/sailfishos-flatpak/flatpak-runner. I tried to list
> all
> > current issues under those repositories.
> >
> > I have also opened a thread at TMO (
> > http://talk.maemo.org/showthread.php?p=1564143) for those who prefer
> that
> > way of communication.
> >
> > Cheers,
> >
> > Rinigus
> >
> > On Sat, Jan 4, 2020 at 10:22 AM rinigus  wrote:
> >
> > > Excellent! If something in kernel config is missing, I expect that you
> > > could use Xperia 10 as a base to check the settings or for Xperia XZ2
> used
> > > by me at
> > >
> https://github.com/sailfishos-sony-tama/android_kernel_sony_msm/blob/hybris-sony-aosp-9.0.0-4.9-tama-sony/arch/arm64/configs/aosp_tama_akari_defconfig
> > >
> > > Rinigus
> > >
> > > On Sat, Jan 4, 2020 at 12:47 AM Adam Pigg  wrote:
> > >
> > >> Ill build it on mido and try it out, thanks!
> > >>
> > >> On Fri, 3 Jan 2020 at 22:45, rinigus  wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> I have submitted PR to libhybris allowing to use Flatpak on hybris
> > >>> devices with the same version serving its main purpose and inside
> Flatpak
> > >>> sandbox: https://github.com/libhybris/libhybris/pull/433.
> > >>>
> > >>> As soon as your device has such libhybris, you could
> > >>>
> > >>> - use https://build.merproject.org/project/show/home:rinigus:flatpak
> to
> > >>> install flatpak, flatpak-runner
> > >>> - run flatpak-extension-hybris to generate Flatpah hybris extension
> at
> > >>> user nemo's home (run as nemo)
> > >>> - install flatpak apps, see instructions at Flathub on how to do it
> > >>> - run them using flatpak-runner
> > >>>
> > >>> Many things don't work, but would be faster to get it fixed together
> > >>> with other devs.
> > >>>
> > >>> Cheers.
> > >>>
> > >>> Rinigus
> > >>>
> > >>> On Fri, Jan 3, 2020 at 12:18 AM rinigus 
> wrote:
> > >>>
> >  Hi,
> > 
> >  just finished the first version of a wrapper for 'flatpak run'
> command
> >  as well, available at https://github.com/rinigus/flatpak-runner .
> Its
> >  based on qxcompositor and it opens new Wayland server before
> running an
> >  application, all explained in README. Device rotation is supported
> and
> >  should be followed.
> > 
> >  So, as it is:
> > 
> >  - we have to resolve libhybris linker issue to make it possible to
> >  distribute.
> >  - keyboard is not supported currently. At present, app has to have
> >  qtvirtualkeyboard support added as in
> > 
> https://doc.qt.io/qt-5/qtvirtualkeyboard-deployment-guide.html#creating-inputpanel
> >  .
> >  - only single-window apps are working well, such as QML developed
> for
> >  mobile
> >  - no sound so far
> >  - probably many other things are missing, haven't bumped into them.
> > 
> >  Essentially, we will have access to the latest Qt, but would have to
> >  write apps for this use. Fortunately, it all goes along SFOS
> programming
> >  and should be simple to convert later to Silica, when/if it catches
> up with
> >  Qt versions.
> > 
> >  I guess we can get better integration after it will be simple to
> >  install on other devices and start using it by others.
> > 
> >  Cheers,
> > 
> >  Rinigus
> > 
> >  On Wed, Jan 1, 2020 at 5:25 PM rinigus 
> wrote:
> > 
> > > Hi,
> > >
> > > wait a bit, I may have a way to simplify setup. Few days ago, after
> > > discussion on IRC, I found a way around disappearance of the
> window when
> > > wrapped into qxcomposer. So, that blocker is over now. Which means
> that we
> > > will be able to craft apps using the latest Qt available in
> 

Re: [SailfishDevel] Flatpak for Sailfish

2020-01-05 Thread szopin
It's device specific? Shame, doubt jolla C can help then. Still hopeful the 
eventual cosmo communicator edition will support it. Any hints what needs to be 
enabled in kernel?

Thanks in advance,
szopin

On Sunday, 5 January 2020, rinigus wrote:
> Hi,
> 
> I have moved all repositories required for Flatpak support to
> https://github.com/sailfishos-flatpak . Documentation is available at
> https://github.com/sailfishos-flatpak/main describing how to install and
> develop using this environment. Issues are expected to be filed fixed under
> https://github.com/sailfishos-flatpak/main and, when appropriate, under
> https://github.com/sailfishos-flatpak/flatpak-runner. I tried to list all
> current issues under those repositories.
> 
> I have also opened a thread at TMO (
> http://talk.maemo.org/showthread.php?p=1564143) for those who prefer that
> way of communication.
> 
> Cheers,
> 
> Rinigus
> 
> On Sat, Jan 4, 2020 at 10:22 AM rinigus  wrote:
> 
> > Excellent! If something in kernel config is missing, I expect that you
> > could use Xperia 10 as a base to check the settings or for Xperia XZ2 used
> > by me at
> > https://github.com/sailfishos-sony-tama/android_kernel_sony_msm/blob/hybris-sony-aosp-9.0.0-4.9-tama-sony/arch/arm64/configs/aosp_tama_akari_defconfig
> >
> > Rinigus
> >
> > On Sat, Jan 4, 2020 at 12:47 AM Adam Pigg  wrote:
> >
> >> Ill build it on mido and try it out, thanks!
> >>
> >> On Fri, 3 Jan 2020 at 22:45, rinigus  wrote:
> >>
> >>> Hi,
> >>>
> >>> I have submitted PR to libhybris allowing to use Flatpak on hybris
> >>> devices with the same version serving its main purpose and inside Flatpak
> >>> sandbox: https://github.com/libhybris/libhybris/pull/433.
> >>>
> >>> As soon as your device has such libhybris, you could
> >>>
> >>> - use https://build.merproject.org/project/show/home:rinigus:flatpak to
> >>> install flatpak, flatpak-runner
> >>> - run flatpak-extension-hybris to generate Flatpah hybris extension at
> >>> user nemo's home (run as nemo)
> >>> - install flatpak apps, see instructions at Flathub on how to do it
> >>> - run them using flatpak-runner
> >>>
> >>> Many things don't work, but would be faster to get it fixed together
> >>> with other devs.
> >>>
> >>> Cheers.
> >>>
> >>> Rinigus
> >>>
> >>> On Fri, Jan 3, 2020 at 12:18 AM rinigus  wrote:
> >>>
>  Hi,
> 
>  just finished the first version of a wrapper for 'flatpak run' command
>  as well, available at https://github.com/rinigus/flatpak-runner . Its
>  based on qxcompositor and it opens new Wayland server before running an
>  application, all explained in README. Device rotation is supported and
>  should be followed.
> 
>  So, as it is:
> 
>  - we have to resolve libhybris linker issue to make it possible to
>  distribute.
>  - keyboard is not supported currently. At present, app has to have
>  qtvirtualkeyboard support added as in
>  https://doc.qt.io/qt-5/qtvirtualkeyboard-deployment-guide.html#creating-inputpanel
>  .
>  - only single-window apps are working well, such as QML developed for
>  mobile
>  - no sound so far
>  - probably many other things are missing, haven't bumped into them.
> 
>  Essentially, we will have access to the latest Qt, but would have to
>  write apps for this use. Fortunately, it all goes along SFOS programming
>  and should be simple to convert later to Silica, when/if it catches up 
>  with
>  Qt versions.
> 
>  I guess we can get better integration after it will be simple to
>  install on other devices and start using it by others.
> 
>  Cheers,
> 
>  Rinigus
> 
>  On Wed, Jan 1, 2020 at 5:25 PM rinigus  wrote:
> 
> > Hi,
> >
> > wait a bit, I may have a way to simplify setup. Few days ago, after
> > discussion on IRC, I found a way around disappearance of the window when
> > wrapped into qxcomposer. So, that blocker is over now. Which means that 
> > we
> > will be able to craft apps using the latest Qt available in Flatpaks.
> >
> > Currently, I am looking into
> >
> > - how we can use regular hybris
> > - making a wrapper similar to qxcomposer for Flatpaks.
> >
> > Shouldn't take too long for an update on status.
> >
> > Cheers,
> >
> > Rinigus
> >
> > On Wed, Jan 1, 2020 at 4:55 PM  wrote:
> >
> >> Could you elaborate on:
> >> > libhybris compiled with specification of default
> >> hybris-ld-library-path,
> >> > content of libexec/droid-hybris added with GL extension.
> >> Is that libhybris build available (and safe to run on main device, or
> >> should I dig out my j1)?
> >> Also not sure what added with GL extension means? Having a browser
> >> that uses up to date webengine would be awesome.
> >>
> >> Thanks and happy new year!
> >> szopin
> >>
> >> On Sunday, 29 December 2019, rinigus wrote:
> 

Re: [SailfishDevel] Flatpak for Sailfish

2020-01-05 Thread rinigus
Hi,

I have moved all repositories required for Flatpak support to
https://github.com/sailfishos-flatpak . Documentation is available at
https://github.com/sailfishos-flatpak/main describing how to install and
develop using this environment. Issues are expected to be filed fixed under
https://github.com/sailfishos-flatpak/main and, when appropriate, under
https://github.com/sailfishos-flatpak/flatpak-runner. I tried to list all
current issues under those repositories.

I have also opened a thread at TMO (
http://talk.maemo.org/showthread.php?p=1564143) for those who prefer that
way of communication.

Cheers,

Rinigus

On Sat, Jan 4, 2020 at 10:22 AM rinigus  wrote:

> Excellent! If something in kernel config is missing, I expect that you
> could use Xperia 10 as a base to check the settings or for Xperia XZ2 used
> by me at
> https://github.com/sailfishos-sony-tama/android_kernel_sony_msm/blob/hybris-sony-aosp-9.0.0-4.9-tama-sony/arch/arm64/configs/aosp_tama_akari_defconfig
>
> Rinigus
>
> On Sat, Jan 4, 2020 at 12:47 AM Adam Pigg  wrote:
>
>> Ill build it on mido and try it out, thanks!
>>
>> On Fri, 3 Jan 2020 at 22:45, rinigus  wrote:
>>
>>> Hi,
>>>
>>> I have submitted PR to libhybris allowing to use Flatpak on hybris
>>> devices with the same version serving its main purpose and inside Flatpak
>>> sandbox: https://github.com/libhybris/libhybris/pull/433.
>>>
>>> As soon as your device has such libhybris, you could
>>>
>>> - use https://build.merproject.org/project/show/home:rinigus:flatpak to
>>> install flatpak, flatpak-runner
>>> - run flatpak-extension-hybris to generate Flatpah hybris extension at
>>> user nemo's home (run as nemo)
>>> - install flatpak apps, see instructions at Flathub on how to do it
>>> - run them using flatpak-runner
>>>
>>> Many things don't work, but would be faster to get it fixed together
>>> with other devs.
>>>
>>> Cheers.
>>>
>>> Rinigus
>>>
>>> On Fri, Jan 3, 2020 at 12:18 AM rinigus  wrote:
>>>
 Hi,

 just finished the first version of a wrapper for 'flatpak run' command
 as well, available at https://github.com/rinigus/flatpak-runner . Its
 based on qxcompositor and it opens new Wayland server before running an
 application, all explained in README. Device rotation is supported and
 should be followed.

 So, as it is:

 - we have to resolve libhybris linker issue to make it possible to
 distribute.
 - keyboard is not supported currently. At present, app has to have
 qtvirtualkeyboard support added as in
 https://doc.qt.io/qt-5/qtvirtualkeyboard-deployment-guide.html#creating-inputpanel
 .
 - only single-window apps are working well, such as QML developed for
 mobile
 - no sound so far
 - probably many other things are missing, haven't bumped into them.

 Essentially, we will have access to the latest Qt, but would have to
 write apps for this use. Fortunately, it all goes along SFOS programming
 and should be simple to convert later to Silica, when/if it catches up with
 Qt versions.

 I guess we can get better integration after it will be simple to
 install on other devices and start using it by others.

 Cheers,

 Rinigus

 On Wed, Jan 1, 2020 at 5:25 PM rinigus  wrote:

> Hi,
>
> wait a bit, I may have a way to simplify setup. Few days ago, after
> discussion on IRC, I found a way around disappearance of the window when
> wrapped into qxcomposer. So, that blocker is over now. Which means that we
> will be able to craft apps using the latest Qt available in Flatpaks.
>
> Currently, I am looking into
>
> - how we can use regular hybris
> - making a wrapper similar to qxcomposer for Flatpaks.
>
> Shouldn't take too long for an update on status.
>
> Cheers,
>
> Rinigus
>
> On Wed, Jan 1, 2020 at 4:55 PM  wrote:
>
>> Could you elaborate on:
>> > libhybris compiled with specification of default
>> hybris-ld-library-path,
>> > content of libexec/droid-hybris added with GL extension.
>> Is that libhybris build available (and safe to run on main device, or
>> should I dig out my j1)?
>> Also not sure what added with GL extension means? Having a browser
>> that uses up to date webengine would be awesome.
>>
>> Thanks and happy new year!
>> szopin
>>
>> On Sunday, 29 December 2019, rinigus wrote:
>> > Hi,
>> >
>> > I would have preferred to stay away from discussion on why do we
>> need/not
>> > need Flatpak on SFOS. But I guess I have to take it as the one
>> working on
>> > making it possible.
>> >
>> > Native apps rely on the libs allowed in the Store and bundle the
>> rest of
>> > them. I presume OSM Scout Server and Pure Maps are exceptions, but
>> they are
>> > built around almost 20 libs bundled with the application and
>> compiled with
>> >