Monday, 2019-06-10

T4<neochapay> @PureTryOut[m] [So I installed Glacier on my Jolla Phone, but …], We don't have surfase window support04:32
*** verin0x0 is now known as verin0x06:33
PureTryOut[m]NeoChapay: I guess that will never come either?06:57
T4<neochapay> why not...if you add suport of this we can start android app into Glacier07:21
T4<neochapay> You can read https://git.merproject.org/mer-core/lipstick/blob/master/protocol/alien-manager.xml07:22
T4<neochapay> and https://git.merproject.org/mer-core/lipstick/tree/master/src/compositor/alienmanager07:22
PureTryOut[m]Uhm yeah sorry, not enough C/C++ knowledge to do that, don't care enough for it either to start learning for it too, as I won't use this phone for much longer08:47
PureTryOut[m]In interest of packaging Glacier for postmarketOS, are there plans of using a Lipstick variant that is compatible with 5.12, e.g. the AsteroidOS one?08:49
PureTryOut[m]*with Qt 5.12?08:49
T4<neochapay> Now i try build with 5.908:53
PureTryOut[m]That's... An improvement lol. Still won't be enough for Qt 5.12 probably.08:54
PureTryOut[m]Has it been tried to run Glacier on the AsteroidOS Lipstick?08:54
r0kk3rzdont think so08:59
T4<neochapay> (Photo, 1077x1031) https://af42kgggd3mfqvgy.tor2web.io/WAVV04hqF2.png Added counters into toolButton09:58
T4<neochapay> https://github.com/nemomobile/qtquickcontrols-nemo/pull/7410:01
kidoPureTryOut[m]: r0kk3rz: the asteroid fork lacks behind a lot of commits behind now. also while upgrading to Qt 5.12 there was a lot of jolla-specific code that I could not test and had to drop (the whole alien dalvik specific protocols etc) I don't think it's used by glacier either but just to mention there are a bunch of stuff missing/modified10:51
PureTryOut[m]A bit annoying that several UI's use several forks of the same library/program... So I want to (eventually anyway) package both AsteroidUI and Glacier. Does that mean I somehow need to make 2 versions of Lipstick work or can some shared one be used?10:53
r0kk3rzyou would likely have to have two versions of lipstick yeah10:56
kidoPureTryOut[m]: well, feel free to merge back the asteroid changes onto a more recent version of lipstick and package one lipstick for both but this will not exactly be a piece of cake10:56
r0kk3rzand two is a weird notion of several :P10:57
PureTryOut[m]Yeah it'll be a pain... It would be nice to have some collaboration between the 2 projects in the future 😉10:58
r0kk3rzuntil now theres not really been a reason for it10:58
T4<faenil> Preventing fragmentation? :)10:59
r0kk3rzthis is open source, fragmentation is expected11:00
T4<faenil> Expected yes, it doesn't mean it always makes sense11:00
T4<faenil> As in, if one can avoid it, why not11:01
kidoI am certainly not against more collaboration but you need to understand that the two projects evolve at different speeds and have different interest.. there are lot of tasks in asteroid that are unfortunately higher priority than having a shared version of lipstick with nemomobile. this is unfortunate but we only have a limited amount of time to invest so we need to choose our priorities11:01
r0kk3rzi dont think its avoidable in this instance11:01
T4<faenil> Of course in this case it's a matter of how much personal time you can invest into avoiding forks11:01
kidonow if this is a high priority for you, you are more than welcome to give it a try and contribute your changes11:02
r0kk3rzyoud need to get asteroid to use sfos lipstick11:02
r0kk3rzwhich is probably more effort than its worth11:02
T4<faenil> kido: of course. See my message. It's personal time so everyone does what he can11:02
kidofaenil: I was answering PureTryOut. no worries I understand your position on this :)11:03
T4<faenil> I was just saying that 'there is' a reason to avoid fragmentation here. We're just missing the time11:03
kidoagreed11:03
T4<faenil> kido: sorry :) glad to hear that :)11:03
T4<faenil> (typing fron the phone, forgive my delay)11:04
T4<neochapay> Where is locusf: ? ^__^12:04
T4<neochapay> @kido [PureTryOut[m]: r0kk3rz: the asteroid fork lack …], You can start fix bugs with 5.9 for start https://build.merproject.org/package/live_build_log/home:neochapay:mer:qt59:mw/lipstick-qt5/latest_armv7hl/armv8el12:05
T4<minlexx> @neochapay [You can start fix bugs with 5.9 for start http …], ```Project ERROR: Unknown module(s) in QT: compositor compositor-private``` … module was renamed in QtWayland: it is now called waylandcompositor AFAIK12:11
T4<minlexx> and TBH is should be written without using private headers12:11
T4<minlexx> using private parts (unstable API) makes is almost impossible to migrate to newer Qt version, as qtwayland is changing fast and a lot in every release12:12
T4<neochapay> @minlexx [and TBH is should be written without using pri …], i know about all of that. But i don't have free time for it. It's was message for many talking guys without any line of code12:13
T4<minlexx> if it is not possible to avoid using private headers then there is no easy solution to this 😢12:13
T4<minlexx> the original author wrote a shitty code and now it is a burden for all12:15
T4<neochapay> All work into https://git.merproject.org/mer-core/lipstick/commits/jb4217012:17
T4<minlexx> (Photo, 613x124) https://af42kgggd3mfqvgy.tor2web.io/3g6MG6Pij8.png hmm, looks like the right direction 🤨12:19
T4<neochapay> i talking not about code. I taliking about sound noize into chanel12:21
T4<minlexx> you are as friendly as always. good luck with finding contributors!12:22
T4<akaWolf> for some people.. the main goal of contributing is to feel yourself significant.. because they are not.12:24
T4<neochapay> bla bla bla just push the code :)12:25
T4<akaWolf> did you read Animal Farm as I suggested?12:25
T4<neochapay> @minlexx [you are as friendly as always. good luck with …], If somebody come to chat and say "hey i have some patch can you push it into upstream" but not...only talking12:26
T4<neochapay> @akaWolf [did you read Animal Farm as I suggested?], I'm not interested to have a dialogue with you. And you know why12:27
T4<akaWolf> :D12:27
r0kk3rz@neochapay: maybe? https://git.merproject.org/mer-core/lipstick/commits/qtwayland-5.612:27
T4<neochapay> @r0kk3rz [@neochapay: maybe? https://git.merproject.org/ …], Why not https://git.merproject.org/neochapay/qtwayland/tree/mer191112:28
r0kk3rzthats not lipstick though12:30
T4<minlexx> @neochapay [If somebody come to chat and say "hey i have s …], My experience with Mer upstream was that:  https://git.merproject.org/mer-core/nemo-qtmultimedia-plugins/merge_requests/2 … With merge requests hanging there for more than a year and no one even cares even to answer the questions (not to review code... that would be too much)12:40
T4<minlexx> what can I say to people wishing to contribute.... GOOD LUCK GUYS12:41
T4<neochapay> @minlexx [My experience with Mer upstream was that:  htt …], i know about you big contribution of mer. I not talk about you. I taking about some rubbling about how cool it would be....12:43
T4<akaWolf> man if you are not satisfied feel free to leave the channel :)12:45
T4<minlexx> maybe adenexter / abranson / chriadam are here or you can poke them )12:45
T4<neochapay> @akaWolf [man if you are not satisfied feel free to leav …], bla-bla-bla12:47
PureTryOut[m]Ok, my questions clearly caused a bit of a... debate... Please do know I'm not saying you guys "have to" spend a lot of time right now to make Lipstick work for both AsteroidOS and Nemo Mobile with the same codebase. I'm just asking if it was something you guys were thinking of doing, and if not, suggesting it as something that _might_ be good for both projects. If I had the technical knowledge to do such things13:37
PureTryOut[m]myself I definitely would, but I do not so the only thing I can do is ask and suggest. I'm not requesting anything from anybody, and I feel that some of the answers were a bit aggressive13:37
T4<faenil> Let's please keep a friendly tone13:46
PureTryOut[m]I wasn't trying the opposite ;)13:51
T4<neochapay> (Sticker, 512x512) https://af42kgggd3mfqvgy.tor2web.io/UrP0Uz01ma.webp13:54
T4<neochapay> https://pastebin.com/DB8Dyz0x15:00
T4<neochapay> Hm.....15:00
T4<faenil> PureTryOut[m]: sorry, didn't see your msg. Yes, my reminder was not for you ;)17:32
PureTryOut[m]Oh no problem :D17:44
r0kk3rzi imagine a lot of work would have to be done to port nemo to pmos anyway23:26
PureTryOut[m]Shouldn't be too bad, most Mer stuff at least compiles fine so far23:28
PureTryOut[m]It's the outdated Qt dependency that's the problem23:28
r0kk3rzthat in itself is probably a lot of work23:30
r0kk3rzand would break compatibility with sfos, so it would be a decision to rebase nemo on pmos rather than mer effectively23:31
PureTryOut[m]Lol I guess23:32
PureTryOut[m]I wonder why SFOS is so far behind with Qt23:32
r0kk3rzmany reasons23:36
r0kk3rzpreviously it was engineering effort, and now its legal reasons23:37
PureTryOut[m]Legal?23:38
r0kk3rzqt changed the licence23:39
PureTryOut[m]From what to what? It's all LGPL-2.1 and GPL-3.023:41
r0kk3rzi think its now lgpl323:41
PureTryOut[m]Even then, why would that be a problem?23:43
r0kk3rzit includes the locked devices clause23:45
r0kk3rzwhich jolla being b2b these days, doesnt want to force their customers to accept23:45
T4<samzn> They have Qt commercial license, no?23:46
r0kk3rzyeah they said that was an option23:47

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!