| *** zbenjamin_ is now known as zbenjamin | 01:35 | |
| *** frinring_ is now known as frinring | 02:02 | |
| *** nyov is now known as Guest24060 | 03:23 | |
| dcaliste | Hello chriadam, would you agree to start our meeting now or earlier than the 7.00 UTC ? | 06:29 |
|---|---|---|
| chriadam | hi dcaliste, sure can have the meeting now if it suits you | 06:29 |
| chriadam | I hope you had a good week? | 06:29 |
| dcaliste | Good, thank you. I wish the same applies to you. | 06:30 |
| dcaliste | Thanks for the meeting with 30 minutes in advance. | 06:30 |
| chriadam | Yes, my week was good thanks | 06:30 |
| chriadam | no problem at all, of course. not sure if flypig or pvuorela are in the office yet, is the only thing | 06:30 |
| chriadam | so the QMF patches all integrated upstream! huge thanks for your work there. glad we finally got those in ;-) | 06:31 |
| dcaliste | We can start with our business then ;) I've replied to your comment on the caldav MR about the detection of the user principal for server in a subdir. | 06:31 |
| chriadam | I will check, thanks | 06:31 |
| dcaliste | Oh, yeh, thanks a lot also to flypig and yourself. It's good that the project still goes on. | 06:32 |
| flypig | I'm around in case you need me :) | 06:32 |
| dcaliste | I'm going to prepare a patch reverting pieces that are not compatible with Qt5.6. | 06:32 |
| chriadam | there are still a couple of leftover commits in the upstream queue which need to be resolved, in particular: https://codereview.qt-project.org/c/qt-labs/messagingframework/+/308665 is fine IMO just needs review | 06:33 |
| dcaliste | But trying to keep as many changes as possible (like the transition to QRegularExpression instead of QRegExp) | 06:33 |
| chriadam | but then this one needs a bit of work from our side first https://codereview.qt-project.org/c/qt-labs/messagingframework/+/287047 | 06:34 |
| chriadam | Matt was hoping that we'd add some more comprehensive hooks for user input in the SSL errors case, but maybe that can happen in a separate PR I think | 06:35 |
| chriadam | (it seems kind of separate to the "ignore all SSL errors" case which that PR enables) | 06:35 |
| dcaliste | I didn't look much at this later one yet. I will in the coming week. | 06:36 |
| chriadam | for the Qt-5.6-compatible thing: that sounds like it might be quite a bit of work.. is there much point? hopefully in future we will be updating our Qt to more recent version, so it might make sense to do that work then instead (e.g. some 5.12 or 5.15 compatible thing, rather than 5.6) | 06:36 |
| chriadam | although Qt version upgrade is always unicorn thing, never quite gets accepted by management.. | 06:37 |
| dcaliste | For 5.6, as you think it's better. But developping patches for the SailfishOS "fork" will make difficult the upstreaming of them due to different code base. I'm afraid so. But yes, it would mean more or less the same amount of work to revert selectively that to upgrade to Qt6... | 06:39 |
| chriadam | hmm, I see what you mean | 06:39 |
| chriadam | ouch, I hadn't considered... | 06:40 |
| Nico[m] | The world would be so much nicer, if we only had to care about 5.15 and 6 compat at this point .-. | 06:40 |
| chriadam | indeed | 06:40 |
| dcaliste | The bright side of it is that it would allow to test part of the migration changes "live", and not all of them at once with a Qt transition at the same time on device. | 06:41 |
| chriadam | that's a very good point | 06:41 |
| dcaliste | (sorry for users as beta testers). | 06:41 |
| dcaliste | I think I will do the revert patching, but at a slow pace. It may not come before next month. | 06:44 |
| dcaliste | If you agree. | 06:44 |
| chriadam | well, they would be beta testers at the future point when qt version upgraded anyway, and like you said, at least this way we'd be testing just the effect of our qt6-transition changes (well, those which don't specifically require qt6) rather than combination of our qt6-transition changes + the qt version update as well.. | 06:45 |
| chriadam | if you are willing to do the work, I definitely see that there is value (mostly: that any changes/fixes we make to jolla qmf will be more easily upstreamable, won't need a complicated rebase before upstream) | 06:45 |
| chriadam | and of course I'm willing to help with that effort if I can, although not sure how much time I will be able to spend on it (I will need to speak to pvuorela I guess) | 06:46 |
| chriadam | as for slow pace: not a problem at all, of course! I mean, the alternative is not doing it at all ;-) thank you. | 06:47 |
| dcaliste | Ok, thanks, I'll ping when I have something ready for git.sailfishos.org. | 06:47 |
| chriadam | tyvm. and if there's anything I can do, please yell | 06:48 |
| chriadam | flypig: ooi do you know if any of our current work is likely to result in changes to our QMF in the near future? e.g. fixes or features planned? | 06:48 |
| chriadam | I can't think of anything off the top of my head, but I guess there's always bugs etc | 06:49 |
| flypig | Nothing immediately springs to mind either. | 06:49 |
| chriadam | cool | 06:49 |
| dcaliste | Ok, that sounds good, it means we have time to slowly import the changes. | 06:50 |
| dcaliste | I've another topic to discuss, related to this bug report : https://forum.sailfishos.org/t/dont-go-to-event-view-on-left-swipe/ | 06:50 |
| chriadam | :-) | 06:50 |
| chriadam | let me check | 06:50 |
| dcaliste | I know it's not your area, but I've found the issue. | 06:51 |
| dcaliste | It's in in lockscreen/LockScreen.qml | 06:51 |
| dcaliste | What is the best ? Give me access to lipstick-jolla-home repository so I can make a PR there or simply put the patch the bug report ? | 06:51 |
| chriadam | pvuorela: ping ^ | 06:53 |
| chriadam | meanwhile, apparently I don't have permission on the forum to view that report :-P | 06:54 |
| dcaliste | It's cbeta restricted ! | 06:54 |
| dcaliste | If you want to test, disable the new "view event on lock screen option", enable "left swipe to event view" and set no lock code. | 06:55 |
| dcaliste | When you wake up the device (tap-tap gesture), swipe right, you arrive to the event view. Swipe left, you arrive to the last opened application or the home screen. | 06:56 |
| dcaliste | Swipe action is reversed on the lock screen. | 06:57 |
| dcaliste | It's due to line 476 in LockScreen.qml | 06:57 |
| chriadam | when pvuorela gets into office I will ask him what the best way forward here is. hopefully can just get you access to l-j-h | 06:57 |
| dcaliste | the x position and the overshoot are not taking the same values in 4.1.0 as previously in 4.0.1 | 06:58 |
| dcaliste | Making the test not behaving as expected before. | 06:59 |
| dcaliste | Thanks for talking to pvuorela about this. | 06:59 |
| chriadam | thank you for investigating | 06:59 |
| dcaliste | With an access to the repo, I can also check if the code changes in LockItem.qml not to use anchors anymore for the EdgeIndicator were intentional. | 07:00 |
| dcaliste | The result is that edge indicators on the lock screen are not animated anymore when swiping there. | 07:00 |
| dcaliste | Investigation of this kind of things in lipstcik itself is a bit tricky. I prefer patching the calendar ;) | 07:01 |
| chriadam | yeah, I understand entirely | 07:02 |
| chriadam | oh, I've poked MartinS again about the jolla-calendar dst transition PR, but afaik he hasn't had a chance to look at it yet. he's been super busy with something recently, but I think that activity will be finished soon, so he should soon have an opportunity to take a look at that one | 07:04 |
| dcaliste | Great thanks to him. We'll seen if he has better ideas than us ! But that's probable ! | 07:09 |
| dcaliste | With the per tiem logging in CalDAV, I'm restarting to work on log viewing. I've come up to a simpler solution than the one I had before, with less changes to the core of Buteo. I'll submitted it soon now I think. | 07:10 |
| chriadam | I saw that there was an update to the "expose SyncProfile to QML" PR but I didn't get a chance to look at it in any detail | 07:12 |
| dcaliste | So don't rush, I will deprecate this one in favour of a new one which provide the same things but much simpler, with almost no changes in Buteo core, only additions. | 07:14 |
| dcaliste | I rebased it on the recent changes and noticed that I could achieve the same result in a much simpler way. | 07:15 |
| chriadam | ah great | 07:15 |
| dcaliste | I was yesterday, so I need a bit more days to check that it's actually providing the same capabilities. | 07:15 |
| chriadam | :-) | 07:17 |
| pvuorela | pong. | 07:17 |
| chriadam | flypig: I guess the next community news letter will be next thursday - would be great to mention dcaliste's contributions to QMF etc there I think | 07:18 |
| pvuorela | not in the office these days, but i could check the repo access. maybe easiest that way. | 07:18 |
| chriadam | pvuorela: tyvm | 07:18 |
| dcaliste | Hello pvuorela, thank you. Like that we can discuss about the fix in a more tracable way. | 07:19 |
| flypig | Talking about the QMF upgrade would be a great thing to include. Do either of you fancy writing something about it? It could even be quite detailed (why was it needed, what does it mean for future patches, etc.). | 07:20 |
| dcaliste | and pvuorela, sorry again for the additional work on the Buteo plugins, but as you said, the good point is a cleaner usage there of the error values. | 07:20 |
| dcaliste | Flypig, I can write something and send it to you (CC chriadam if he would like to amend it), would next Friday be ok for it ? | 07:22 |
| chriadam | sounds good, thanks | 07:22 |
| flypig | That would be great, and next Friday would be perfect. | 07:22 |
| flypig | It'd be a good opportunity to show work going on behind the scenes that is essentially hidden for most people. | 07:23 |
| chriadam | :-) | 07:24 |
| chriadam | were there any other topics to discuss today? anything I have forgotten or need to follow up on? | 07:24 |
| pvuorela | dcaliste: np, luckily the fixes were mostly simple even if they were needed in many places :) | 07:24 |
| flypig | dcaliste, is there anything else that could/should be included that you've been working on, or that you're aware of? | 07:25 |
| dcaliste | flypig, I don't think I've got anything ready yet. I need to finish the various things that I have started and that are stale in the middle at the moment ;0 | 07:29 |
| flypig | Okay, no problem. We can take another look in the future. | 07:30 |
| dcaliste | chriadam, I think, we've addressed all the points I had in mind today. Do you want to speak about something else I would have forgotten ? | 07:34 |
| chriadam | I had no other topics to discuss. I will create a bug for the caldav PR and get it merged. I just looked at https://forum.sailfishos.org/t/nextcloud-account-creation-failed-calendar-make-it-fail/1655/17 and I wonder if that's related? | 07:35 |
| chriadam | we may need to resolve something in jolla-settings-accounts ? not sure | 07:36 |
| chriadam | It sounds like in this case it is failing at account creation time | 07:38 |
| dcaliste | Yeh, the discovery code is duplicated and different in CalDAV and account creation. | 07:39 |
| dcaliste | I can see if I can find a way to reproduce the faulty behaviour... I'm adding a bookmark for this one. | 07:41 |
| chriadam | I have created JB#53905 to track that one and will ping Bea about it also | 07:42 |
| chriadam | well, nothing else from me. flypig or pvuorela did you have anything to discuss? | 07:44 |
| flypig | I don't think so. | 07:44 |
| pvuorela | i don't have. | 07:45 |
| chriadam | ok, if nothing else, thanks for your time and effort as always dcaliste, and flypig and pvuorela too of course ;-) | 07:46 |
| chriadam | have a great week! | 07:46 |
| * chriadam -> away, gnight | 07:46 | |
| flypig | Same from me | 07:46 |
| dcaliste | Thanks all ! | 07:46 |
| Malinux | Hi. Why is it in the calendar app, the line: calendar Personal is grayed out? I want to move my events to the nextcloud calendar, but it's possible only to choose if I make a new event | 10:15 |
| ggabriel | Malinux: good question, I did export mine somehow in the past, then imported them in nextcloud (I used something else in fact, but that was the workflow that I used to migrate to different providers) | 12:05 |
| ggabriel | yeah, I forgot about all the CLI tools... I would look in sailfishos.org if I were you, or search/post in the forums | 12:10 |
| Malinux | yeah, It's not that I can't use cli tools, but I think there should be an easy way to do it within the gui and also to change what calendar to put an event in after it is created in another calendar :) | 12:11 |
| ggabriel | so, I read that you may be able to change the provider in future versions, yes | 12:11 |
| ggabriel | but, still, that would be on an event-per-event basis | 12:12 |
| ggabriel | if you wish you migrate everything that you have in personal to nextcloud, that would be a bit cumbersome | 12:12 |
| ggabriel | I admit I forgot what I did and when I did it... maybe jolla didn't exist when I finally decided to use some caldav backend for my calendars | 12:14 |
| Malinux | maybe :) | 12:15 |
| Malinux | like in manage calendars, there should be an option. export calenadar as (and then support some formats) But gonna find the cli-tools for now then :) | 12:16 |
| * ggabriel just noticed 2 personal calendars switched off in manage calendars lol | 12:17 | |
| ggabriel | Malinux: good luck - can't promise there's such a tool now, try to make a backup and see if the format is vcalendar, maybe you're in luck | 12:18 |
| ggabriel | that would be trivial to import into nextcloud | 12:18 |
| Malinux | Think I can't make backups with the backup-client iirc. It always hang on the backup calendar part | 13:09 |
| Malinux | hehe, switched off :) I can easly turn off or enable calendars there, but I just don't understand why I can't either switch calendar pr event, or even the entire caleandar easly, though, I hope as mentioned before, there will be an option for it | 13:10 |
| ggabriel | Malinux: it doesn't do it because it isn't implemented. Expect to be able to do it per event, but certainly not per calendar. Nobody does that | 13:56 |
| Malinux | I can't even do per events :p | 14:30 |
| *** vilpan is now known as Guest70305 | 14:39 | |
| *** Guest70305 is now known as vilpan | 14:39 | |
| ggabriel | Malinux: when I say "expect to", I mean in the future - there is mention of this in the forums | 16:09 |
| Malinux | ah, I haven't seen. sorry :L) | 17:13 |
| Malinux | eh, :) I mean | 17:13 |
| ggabriel | yeah, no problem. how many events do you have anyway? I was thinking that maybe it's worth just enabling personal and personal[nextcloud], put the new ones in the latter, and let the former ones die a natural death as time itself makes them irrelevant | 17:36 |
| *** SpeedEvil is now known as Guest31881 | 21:00 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!