some feedback from a mobile application development team

[Sebastian Kügler]

On Wednesday, January 06, 2016 10:48:10 AM Dirk Hohndel wrote:
> On Wed, Jan 06, 2016 at 04:39:33PM +0100, Marco Martin wrote:
> > On Wednesday 06 January 2016, Dirk Hohndel wrote:
> > > Building for Android is painful (as Sebastian will confirm). Adding
> > > something where an application after being started downloads other
> > > components... not going to happen. At least not for Subsurface. I want
> > > to
> > > be able to offer the user an .apk that works.
> > >
> > > There apparently is a way to separate the Qt libraries from your apk.
> > > I'm
> > > not doing that either
> >
> > no, i was meaning doing that at build stage (the big build script) it
> > would  still create a single big apk
> 
> So this is more a question about Subsurface sources. I'll defer to
> Sebastian to some extend. Right now it's clear that there is a certain
> delta between upstream and what we have in Subsurface. I can see the
> benefit of just being able to use upstream and will be happy to figure out
> how to do that in the build script.

The pending changes are now upstreamed, we can 'blindly' pull mobilecomponents 
into subsurface again.

There were two issues:
- the black icon, has to do with a shader, since it's only in the Android-
specific bits, I disabled the active effect until we find a solution
- the keyboard geometry in Android was wrong, I made our algo to deal with it 
more lenient

Both are in plasma-mobile master.
-- 
sebas

http://www.kde.org | http://vizZzion.org