#nemomobile log for Wednesday, 2020-03-11

T42<DibyaXP> @neochapay05:58
T42<DibyaXP> Awesome work man.05:58
T42<DibyaXP> QT5.12 , we can have all KDE desktop , thought may need adjustment .05:58
T42<DibyaXP> Finally sailfish getting competitor .05:58
T42<DibyaXP> Did you try the wallpapers I emailed you last time ?05:58
T42<neochapay> @DibyaXP [@neochapay05:59
T42<neochapay> Awesome work man.05:59
T42<neochapay> QT5.12 , we can …], Yea i got it :) i add it into new release05:59
T42<neochapay> @eekkelund can you create mr into devel branch with changes for qt5.1207:26
T42<neochapay> without compatibility old version of qt07:27
T42<starbuck2018> @DibyaXP [@neochapay08:28
T42<starbuck2018> Awesome work man.08:28
T42<starbuck2018> QT5.12 , we can …], That is first step. To really make nemo compatible it is best to make it run independent, so it can be shipped with pmos, arch, manjaro, ubuntu/neon, fedora, suse arch...08:28
T42<neochapay> @starbuck2018 [That is first step. To really make nemo compat …], it's first steep to remove old code ^_^08:33
T42<starbuck2018> @neochapay [it's first steep to remove old code ^_^], Yes 👍08:38
T42<abranson> @starbuck2018 [That is first step. To really make nemo compat …], There's a large amount of mobile specific middleware in the sailfish core. I think you might lose a bit too much there. It's one thing to make glacier portable, but nemo's a lot more than that with sailfish underneath.08:38
T42<abranson> That set of middleware can be traced back through Sailfish, Meego and Maemo. It's a mature mobile Linux base.08:39
T42<abranson> That's also actively maintained as such08:39
T42<neochapay> i think we dont get many pain with run dsme/mce/ofono and other stuff into another distr08:40
T42<abranson> I think there's more than just those. Lipstick for instance, and it's all interdependent. but if all your swapping is the common packages beneath, then why bother?08:44
T42<starbuck2018> @abranson [I think there's more than just those. Lipstick …], Some people like arch rolling, some people like debian, not all like mer09:41
T42<starbuck2018> Hence there is pmos, alpine, voyager, fedora, etc.09:41
T42<starbuck2018> People like freedom09:41
T42<abranson> Right, but there's a danger of over abstraction if you cast the net too wide. I guess it's a question of identifying what nemo is, and how much of sailfish is useful upstream of it.09:45
T42<abranson> that sailfish core is just a set of packages. some are shared with other distros, some are patched, some are individual to it. but changes are made to them as a whole by Jolla, and undergo CI and testing to make sure they work together. doing that for n other distros is not trivial.09:47
T42<NotKit> on other hand, same can be said about other large projects like KDE Plasma and frameworks09:50
T42<NotKit> normally it's distro-specific patches + PRs09:51
T42<neochapay> @NotKit [normally it's distro-specific patches + PRs], if you see into my gitlab repo you can see that ^_^09:51
T42<abranson> I guess nemo means different things to different people. The simple description states that it's an alternative UI framework and homescreen on top of the FOSS packages of Sailfish, which is much smaller than something like KDE plasma.09:54
T42<NotKit> (Photo, 1280x720) https://irc.thaodan.de/.imgstore/F4kHHkOKVF.png imagine if it could like on this on some modern base like Arch or pmOS :)10:03
T42<aa13q> @NotKit [<reply to media>], yeah, it would be awesome :)10:04
* PureTryOut[m] is planning to package Glacier for pmOS once it works on Qt 5.14.1+10:05
T42<neochapay> i think when we update to 5.12 it will simple10:14
T42<neochapay> And i try use maximal upstreamed Qt and other10:14
PureTryOut[m]Yup, sounds great!10:14
PureTryOut[m]And once Qt 5.12 support is in, I indeed think it won't be hard to update further either10:15
T42<Sam %lastname%> @NotKit [<reply to media>], this picture hurts me everytime10:16
T42<neochapay> (Photo, 960x1280) https://irc.thaodan.de/.imgstore/kf6qLYGMpP.png10:29
T42<NotKit> is leftmost one Nexus 5?10:37
T42<Sam %lastname%> (Document) https://irc.thaodan.de/.imgstore/QvKXy5KGoT.mp410:37
T42<neochapay> @NotKit [is leftmost one Nexus 5?], yeap10:37
T42<neochapay> @eekkelund ping13:25
T42<meierrom> @Sam %lastname% [this picture hurts me everytime], Why so?13:30
*** verin0x1 is now known as verin0x14:17
*** verin0x9 is now known as verin0x14:24
T42<starbuck2018> @NotKit [<reply to media>], That'd be awesome14:55
T42<neochapay> Ok i fixed build of QtPim and statefs-qt5....maybe today or tomorrow i can make image for pinephone with 5.1214:56
T42<neochapay> for fix all failed we need revert commits in qttools for qtdoc....because it needed clang....14:58
T42<starbuck2018> @abranson [that sailfish core is just a set of packages. …], What packages are individual though?14:59
T42<starbuck2018> If pinephone/pinetablet can run any normal linux as arm img (so not needed any extra layer like libhybris or android), and using nemo as tablet ui without any phone functionality, what set of packages is needed?15:06
T42<starbuck2018> I wonder if UT with mir is easier to run on other base than ubuntu or nemo with lipstick on other base than mer...15:07
T42<neochapay> @starbuck2018 [If pinephone/pinetablet can run any normal lin …], PinePhone can run nemo https://www.youtube.com/watch?v=M3n4ORBRP1M15:07
T42<neochapay> And i can send sms by pinephone on nemo. After finish port to Qt5.12 i whant to fix all sms/voicecall applications15:08
T42<neochapay> Ok...current status of build: succeeded: 108 failed: 10 unresolvable: 315:12
T42<starbuck2018> @neochapay [PinePhone can run nemo https://www.youtube.com …], Yes, i mean any other than mer... Of course mer as distro can be made to run on many hw, or nemo + software stack can be run on many distro bases, so i meant nemo doesnt need a special distro base like mer or yocto or linaro to be run on pinephone... Arm based dev15:14
T42ices and hw got more powerful so "normal" distros can be used as arm versions without much penalties these days. So neon/ubuntu runs okay or debian/raspbian is fine, as is opensuse now preparing for arm and fedora :)15:14
T42<neochapay> @starbuck2018 [Yes, i mean any other than mer... Of course me …], I think main requires mer version of ofono, mce, dsme but other requires like statefs may be dropped and rewrited15:16
T42<AJSlye> @neochapay [Ok...current status of build: succeeded: 108 f …], Hopefully you'll be able to get those fixed soon. 😉15:16
PureTryOut[m]Oh Nemo requires non-upstream versions of Ofono?15:17
PureTryOut[m]That'll be a problem on at least postmarketOS...15:17
T42<neochapay> @PureTryOut[m] [Oh Nemo requires non-upstream versions of Ofon …], Yeap ^_^15:17
T42<neochapay> i don't think so...because we can use standarts dbus ifaces15:18
PureTryOut[m]Huh, are you contradicting yourself now? Does or does Nemo not require a non-upstream version of Ofono? What would happen if we'd try to run it with regular Ofono?15:20
T42<neochapay> Now we use mer specific version of ofono. And yes we know it not good way. We need to fix it in future.15:21
T42<minlexx> likely even dbus interfaces won't match (I may be wrong)15:21
PureTryOut[m]Hmm ok, as long as it's an issue you're aware off and want to fix eventually15:22
T42<neochapay> steep by steep i whant use only upstream packages15:23
T42<DibyaXP> @neochapay15:23
T42<DibyaXP> Is their any way to make app opening faster in Nemo ? It's kinda slow on Xperia X incomparison to android .15:23
T42<DibyaXP> May be it can improve by remove app opening animation15:23
PureTryOut[m]neochapay: awesome! Can't wait!15:25
T42<neochapay> @DibyaXP [@neochapay15:26
T42<neochapay> Is their any way to make app openi …], we don't have open animation hehe ^_^ but yea i think we have some ways to make start faster15:26
T42<DibyaXP> What about those white dots when I click on any app15:27
*** verin0x8 is now known as verin0x15:42
T42<abranson> @starbuck2018 [Yes, i mean any other than mer... Of course me …], I'm not so sure that it's a good idea to assume that a mobile device can use a desktop base even these days. Things such as power consumption, memory usage and the dependency on hw acceleration due to relatively weak cpu power and battery saving will always be issu15:52
T42es.15:52
T42<abranson> These are things that many people have underestimated in the past when launching their mobile devices, and is a heavy contributor to why so many of them fail.15:52
T42<abranson> mobile linux is strewn with the corpses of failed startups who thought they knew best and didn't learn from the mistakes of others.15:53
T42<Sam %lastname%> @abranson [mobile linux is strewn with the corpses of fai …], yup20:42
T42<Sam %lastname%> which begs thee point why even use linux20:43
T42<Sam %lastname%> I'm more focused on delivering something that gives more value to the end user20:43
T42<starbuck2018> @neochapay [steep by steep i whant use only upstream packa …], You have a list of how many non-upstream packages current nemo relies on? Ofono,...?20:44
T42<abranson> same as with the desktop. the number one reason for failures is when different groups squabble and don't work together. forking can be a huge boon to development, but it kills a lot more of it.20:44
T42<abranson> @starbuck2018 [You have a list of how many non-upstream packa …], some of these projects are just packaged upstreams, some have patches, some are maintained by sailfish: https://git.sailfishos.org/20:46
T42<abranson> not all of them will be used in nemo, but a lot of them will. that's most of the foss packages in sailfish. the rest is on github.20:46
T42<abranson> I guess the sfos fork on connman is needed in nemo?20:47
T42<starbuck2018> @abranson [mobile linux is strewn with the corpses of fai …], Agreed. So my estimate is "mainstream" mobile linux will happen when, like on desktop, taking a common base and run it properly with upstream shared projects without big penalties is no longer an issue. I also agree this cannot be solved properly longterm by just o21:04
T42ne project, thats why many fail. But with existance of pinephone/pmos, you see many projects come together and work on support, like mainline kernel, ofono, etc. so phosh, ubports, plamo can all use same components on similar stack up to a certain point, just like with desktop linux. If you see how well main distros work on pinebook also for batter21:04
T42y, etc., most phones are an even better arm computer than pinebook, with same/ or better arm board, so i think being free to choose and run different platforms without big hassle is what makes people embrace pinephone/pinetab. It is not there yet and wont be too soon for phone, but with time it will mature and get there, and the old approach of clo21:04
T42sed/limited hw combined with "special distros" is hopefully no longer needed (of course it is nice to also run those on that hw to compare or have ultra-optimized functionality, but its maintainance cost of patched/non-upstream version vs. using standard, where the latter could still take 1-2 years to get there). But just seeing the interest of peo21:04
T42ple wanting to easily run a full debian/arch/ubuntu on pinephone because its fun and allows to go experiment shows a trend, even if not useful yet as daily device. So maybe purism was 1-2 years too early before its feasable, but maybe they prove their pureos stack on debian is good enough.21:04
T42<Spikerguy> 👍21:06
*** verin0x6 is now known as verin0x21:49

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!