| *** jrt is now known as Guest50529 | 02:07 | |
| rinigus | Looks like Nemo dozed off for a weekend. Let's hope it will wake up soon. neochapay, would you mind adding i486 to nemo-ux arch selection at obs? Allowing to test in emulator | 06:59 |
|---|---|---|
| SergeyChupligin[ | rinigus https://build.merproject.org/project/monitor/home:neochapay:nemo-ux куфвн | 07:11 |
| SergeyChupligin[ | * rinigus https://build.merproject.org/project/monitor/home:neochapay:nemo-ux ready | 07:11 |
| rinigus | Sergey Игоревич Chupligin: thank you very much! | 07:20 |
| rinigus | strange, got your yesterday replies just now. | 07:22 |
| SergeyChupligin[ | Different timezones? | 07:22 |
| rinigus | :) | 07:23 |
| SergeyChupligin[ | hmmmm obs so bugged | 07:23 |
| SergeyChupligin[ | on build it says 403 o_O | 07:23 |
| SergeyChupligin[ | WTF ? | 07:23 |
| SergeyChupligin[ | https://build.merproject.org/package/live_build_log/home:neochapay:nemo-ux/lipstick-glacier-home-qt5/sailfish_latest_i486/i586 | 07:23 |
| rinigus | retry/ | 07:23 |
| rinigus | ? | 07:23 |
| SergeyChupligin[ | trying | 07:24 |
| SergeyChupligin[ | not changed.... | 07:25 |
| Pablo[m] | Telegram was malfunctioning yesterday | 07:25 |
| rinigus | Sergey Игоревич Chupligin: no worries, probably something is broken (hdd full or similar?). I can probably add your repo to my build env and then build lipstick locally | 07:27 |
| rinigus | Pablo: thanks, that explains it | 07:28 |
| rinigus | sms sending: is that related to some closed src components used for it on sfos? | 07:28 |
| rinigus | going through nemomobile issues, cannot find anything regarding sms: https://github.com/search?q=is%3Aissue+user%3Anemomobile+is%3Aopen+sms | 07:40 |
| rinigus | Sergey Игоревич Chupligin: managed to make it work with local build. | 08:20 |
| rinigus | thanks for making i486 arch - makes it simple to test the rest | 08:20 |
| SergeyChupligin[ | <rinigus "sms sending: is that related to "> That bug. I don't know how send sms correctly 😅 | 08:25 |
| rinigus | I see, that sms bug can b looked at :) | 08:39 |
| * rinigus sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/VnJqiPgsuWBjPRyUOqXjbaQf > | 08:39 | |
| SergeyChupligin[ | Yea we use own components | 09:01 |
| rinigus | Sergey Игоревич Chupligin: kirigami has qt 5.12 as a requirement, if I remember correctly (maybe 5.11). so switch could be a subject after 5.12 update. | 09:40 |
| rinigus | I wonder if you could make a separate issues/docs repo in github to collect issues such as sms bug. that would simplify helping you | 09:41 |
| rinigus | nemo is probably missing all accounts stack (email/calendar/contacts dav). as those are (partially?) closed source on sfos | 09:43 |
| SergeyChupligin[ | All core sfos app is closed | 09:44 |
| rinigus | Sergey Игоревич Chupligin: exactly. so those are the ones that are needed | 09:45 |
| rinigus | there was a list somewhere with closed/open components for sfos | 09:45 |
| rinigus | that's a decent list: https://together.jolla.com/question/167645/open-source-roadmap-from-the-community-point-of-view/ | 09:47 |
| SergeyChupligin[ | And now i only one who write app on nemo | 09:49 |
| SergeyChupligin[ | I don't have so much free time :) | 09:49 |
| matt[m]2 | <SergeyChupligin[ "And now i only one who write app"> Locusf not here anymore? | 09:50 |
| locusf | still here just not too active | 09:50 |
| PureTryOut[m] | You did say you were going to use Kaccounts for accounts stuff no? | 09:50 |
| rinigus | Sergey Игоревич Chupligin: I am considering to help. while I have a maps stack to take care of and have to use some time for that, I can maybe allocate some time to work on nemo. from "free" time :) | 09:52 |
| rinigus | as a part of that, is looking what's broken, what's needed, what is missing to make nemo as a daily driver | 09:53 |
| matt[m]2 | Ok nice 😊 | 09:54 |
| rinigus | to reduce the load on app development, I was asking regarding kirigami. as kirigami would allow you to run plasma apps => larger number of devs working on it | 09:55 |
| SergeyChupligin[ | Sounds good | 09:55 |
| matt[m]2 | Wow rinigus that's great you will help sergey with nemo | 09:57 |
| SergeyChupligin[ | I don't like kirigami it so androidifly hehe | 09:58 |
| matt[m]2 | is kirigami the ui of plasma? | 09:59 |
| rinigus | matt: don't jump to early conclusions and wait for the first PR | 10:02 |
| rinigus | Sergey Игоревич Chupligin: that's the default UI for it. and I agree with your assessment. but, we can style it differently and make it way closer to silica | 10:02 |
| rinigus | (there are some connectivity issues with matrix...) | 10:06 |
| SergeyChupligin[ | Why not use own components? | 10:06 |
| matt[m]2 | I tried 😜 | 10:08 |
| rinigus | It takes time to develop components and port apps to them. If you switch to kirigami, style will be applied to all of them and you have pool of kirigami apps looking native. | 10:08 |
| rinigus | For example, can we swipe pages in Nemo components? Took a while for it to be developed in kirigami | 10:09 |
| AndreaBernabeifa | rinigus: great to hear you're considering contributing to Nemo :) it's a massive effort, I'm always unsure whether we shouldn't just help some other bigger project instead | 10:55 |
| rinigus | Andrea Bernabei (faenil): reasons I am considering Nemo. there are two other major projects that could be considered: Ubuntu Touch and Plasma Mobile. UT is out for me as it is stopping all apps in the background making it harder to write something like osm scout server/pure maps combo. In general, I prefer to be in charge of which apps are running and which are stopped. In this respect, SFOS/Nemo approach suits me. | 11:06 |
| rinigus | Plasma Mobile - I don't like their UI choices (buttons at the bottom as on android), cannot comment on the internals as I haven't looked into them. Nemo ticks UI expectations and is built on the same working basis as sfos. as sfos parts are already maintained and can be collaborated on, that leaves "just" closed source components. | 11:06 |
| rinigus | but to understand the size of the task, how to collaborate with others on them, some issue tracker is needed. listing the missing parts and how to approach them | 11:07 |
| rinigus | also, as you could see from my questions above, I am not sure I grasp gestures and approach to the design of the apps. | 11:07 |
| PureTryOut[m] | I agree, sharing components with other systems is always a good thing. You have to do less work yourself and benefit from the changes made as a whole. | 11:11 |
| PureTryOut[m] | And yes you can do a lot with styling | 11:11 |
| PureTryOut[m] | Especially if you want to attract app developers it's better to have to tell them not to use another set of components for <insert platform to support here> | 11:11 |
| PureTryOut[m] | * Especially if you want to attract app developers it's better to have to tell them not to use yet another set of components for <insert platform to support here> | 11:11 |
| rinigus | I had experience of porting Pure Maps and OSM Scout Server from Silica to Kirigami and Ubuntu Touch. In many respects, all the components were similar. When I was missing something in Kirigami, I asked for it and it got implemented/fixed rather quickly. From the top of my head, maybe in weeks/days. So, from app writer POV, it is way better to work with just one set, as PureTryOut stressed above | 11:16 |
| rinigus | It seems to me that Nemo could win by reusing Plasma Mobile work and working together on apps. As it already wins from having SFOS working on the base. | 11:17 |
| PureTryOut[m] | Yup, completely agree | 11:17 |
| rinigus | but to be constructive and get some kind of overview, some kind of issue tracker and design docs are needed. not sure I mentioned it above.... :) | 11:18 |
| rinigus | Andrew Branson : makes sense. In this respect of we learn how to style the apps including kirigami ones, we could in better state with sfos as well. | 13:03 |
| rinigus | Again, more collaboration between sfos/plasma would be handy. But there, closed components, such as silica, stand on the way | 13:05 |
| rinigus | As for sfos qt update, 'eventually' is a good word to describe it. Right now, on the basis of the feedback from meetings, I have a feeling there is nobody working on it. | 13:09 |
| SergeyChupligin[ | https://build.merproject.org/project/monitor/home:neochapay:mer:release:2020.05:core OH YEA!!!!!!!!!!!!! | 13:09 |
| SergeyChupligin[ | core is ready | 13:09 |
| SergeyChupligin[ | qt-5.12 is comming | 13:09 |
| SergeyChupligin[ | all base sfos components have me for suppoting Qt-5.9+ | 13:11 |
| rinigus | Stand corrected, except capitan Nemo! | 13:11 |
| AlexeyMinnekhano | Qt 5.9 LTS support ended in 2020-05-31 | 13:12 |
| SergeyChupligin[ | Now i got 5.12 on release 2020.05 | 13:13 |
| AlexeyMinnekhano | 5.12 LTS support ends in 2021-12-05 | 13:13 |
| AlexeyMinnekhano | you still have some time 😂 | 13:13 |
| SergeyChupligin[ | i think update 5.12->5.14 will be simplicity 5.6-5.12 ^_^ | 13:14 |
| SergeyChupligin[ | * i think update 5.12->5.14 will be simplicity 5.6->5.12 ^_^ | 13:14 |
| PureTryOut[m] | I had Nemo working (or at least compiling) on Qt 5.14 already with the Qt 5.12 patches. Although the mouse didn't seem to work | 13:23 |
| PureTryOut[m] | And Qt 5.15 is already out btw | 13:23 |
| Manuel[m] | Nice | 13:45 |
| Manuel[m] | Will Nemo change its base to something like arch or something with more gnu like if the distros have better mobile support | 13:45 |
| Manuel[m] | * Will Nemo change its base to something like arch or something which more gnu like if the distros have better mobile support | 13:45 |
| AndrewBranson[m] | rinigus: as far as I know people are working on finding a way to license later versions for both community and commercial use, without forking sfos completely. I don't think that's ever stopped. It's nearly been solved a couple of times, but not in a way that everyone involved is happy with. | 13:47 |
| PureTryOut[m] | Manuel: what's not GNU-like about Sailfish? Why would Nemo change it's base if the current one works well enough? | 13:47 |
| rinigus | Andrew Branson: if they have worked for so long, maybe there is no good solution, unfortunately | 13:52 |
| Manuel[m] | Sry gnu like was false I mean something up to date with new kernel and packages | 13:52 |
| Manuel[m] | More like on the desktop and not like Ubuntu touch or sailfish | 13:52 |
| AndrewBranson[m] | kernel is nothing to do with sfos - that's always device specific on mobile. | 13:52 |
| AndrewBranson[m] | but sfos packages aren't that out of date anymore. Only Qt really stands out as old these days. | 13:53 |
| Manuel[m] | But if I understand correctly you can't run as example gimp on sfos because of dependses | 13:53 |
| PureTryOut[m] | Manuel: You just mean a more traditional Linux distro model with a package manager to install apps and libraries from then? I'm not entirely sure what the benefit of that would be for Nemo | 13:54 |
| PureTryOut[m] | Besides, if you just want Glacier, that is possible on e.g. Manjaro or postmarketOS (Alpine Linux), both distros have WIP ports for it | 13:55 |
| Manuel[m] | Yes I exactly mean this sry for my unprofessional description | 13:55 |
| rinigus | Manuel: eventually, apps that are reasonable for mobile get over. its "just" an issue with old Qt. as for gtk mobile apps, they are relatively new if we talk about purism efforts. | 13:56 |
| rinigus | as for gimp, not sure what can I do with it on mobile screen | 13:56 |
| Manuel[m] | K the benefit would be compabilitie but I think with a base change you loose the sfos compability Wich also inst great | 13:57 |
| Manuel[m] | <rinigus "as for gimp, not sure what can I"> Only a example because I can't explain it better | 13:57 |
| PureTryOut[m] | Compatibility how? You can just package GIMP for SFOS you know, it just won't be really usable on such a tiny screen | 13:59 |
| Manuel[m] | I understand sry for my unneeded discussion | 14:00 |
| AndrewBranson[m] | rinigus: if nothing would change then it might not get solved, but as more time passes 5.6 gets more out of date, unsupported and insecure, so the variables change. it'll get solved eventually. | 14:07 |
| rinigus | coming back to nemo discussion. I will take quick(ish) look into kirigami styling as I think it could be a way forward and will report back. Sergey Игоревич Chupligin , maybe at some point you can find time and either make repo fr issues or tell how the issues are expected to be filed. as for issues, we can all help with filing them to the best of our knowledge | 14:07 |
| rinigus | Andrew Branson: true, time does change the variables. and in the case of qt, makes it more critical | 14:08 |
| -Shieldy[m]- (9 + 9) Nguyen Ngoc, please, send the solution to the arithmetic operation provided within the time amount specified to this group, otherwise you will be kicked. Thank you! (240 sec) | 15:43 | |
| AndreaBernabeifa | <rinigus "Andrea Bernabei (faenil): reason"> I see..yeah, makes sense :) | 18:42 |
| AndreaBernabeifa | <rinigus "coming back to nemo discussion. "> In the good old times, i.e. when Nemo was born, we used Nemo/Mer bugzilla...not sure if that's still the case. | 18:43 |
| AndreaBernabeifa | * In the good old times, i.e. when Nemo was born, we used Nemo/Mer bugzilla...not sure if that's still the case. | 18:44 |
| AndreaBernabeifa | I recently got some emails about bugs I was working on 6-7 years ago and that had now been closed by Jolla employees :D | 18:44 |
| rinigus | Andrea Bernabei (faenil): these days would be probably easier to make special repo in github and collect issues there. | 18:50 |
| rinigus | (where they closed as stalled or resolved?) | 18:50 |
| rinigus | Sergey Игоревич Chupligin: already with small projects, like ports to devices, its good to have some dedicated docs and issues repository. that repo is usually pinned in the organization making it easy to find. later the issues can be passed down to the respective component by those who know better. example issue: work on email client | 20:31 |
| rinigus | would be also handy to know what's the difference between https://github.com/nemomobile and https://github.com/nemomobile-ux ... | 20:55 |
| *** tepper.freenode.net sets mode: +o faenil | 21:59 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!