| mal | akrosi: maybe something like this is missing https://github.com/sonyxperiadev/device-sony-common/pull/891/files but of course different content and paths, not sure how to get those values though | 00:17 |
|---|---|---|
| mal | there appears to be verizon firmware files on the device | 00:18 |
| akrosi | well, ordered an xperia 10 III. I'll see if I can get VoLTE working; if not, it's not too big of a deal as I've wanted an excuse to change carrier for a while now | 02:50 |
| akrosi | has anyone tested emergency alerts? is there any system in place for their delivery? specifically referring to the Wireless Emergency Alert system in the US that makes phones screech whenever a child goes missing or there's a tornado nearby | 02:51 |
| *** amccarthy is now known as Guest3543 | 03:33 | |
| *** amccarthy_ is now known as amccarthy | 03:33 | |
| dcaliste | Good morning pvuorela, thanks a lot for the various reviews these last days. | 07:03 |
| pvuorela | dcaliste: good morning. quite a bit of code there to go through :) | 07:03 |
| dcaliste | Indeed, so let's start with pending questions in #60: should we support an 'after' argument in the listing routines ? | 07:06 |
| dcaliste | With the backend, there is no calendar stuff, so all functions are returning lists of Incidences. There are the 'incidences(nbuid, uid)' and the 'incidences(qdate, qdate)'. But also the 'deletedIncidence(nbuid)'. | 07:08 |
| dcaliste | The question is thus, should we add a 'deletedIncidences(qdate, qdate)' ? Or even a 'created(qdate, qdate)' and a 'modified(qdate, qdate)' for instance ? | 07:09 |
| dcaliste | Such routines are currently used by some sync plugins (the Google one and the EAS one I guess). | 07:09 |
| dcaliste | But, it's possible not to use them, as in the CalDAV sync plugin. | 07:10 |
| dcaliste | In the Google plugin, at the moment, it is even done in a redundant way, since we list in the same routine (at the same time), all incidences, and modified incidences since. | 07:11 |
| pvuorela | i wouldn't think they should much affect the code except existing? one thing could be that if they are removed, i could rather have sync plugins remove the usage and port to new storage api separately than everything at the same time. | 07:12 |
| henk | I’m trying to install "Maliit Presage Plugin" via chum-gui but it gives some error message I don’t understand: »the installed libpresage-someversion requires 'presage-data', but this requirement cannot be provided«. the package "Presage Data" is installed, though. any advice how to get more info to figure out what’s wrong? | 07:12 |
| dcaliste | This I agree, indeed. That's why, I kept sqlite accessors in the backend to keep support for ExtendedStorage. | 07:13 |
| dcaliste | Like that, rework of the API through CalendarStorage and MultiCalendarStorage can go on, while Buteo sync plugins are still buildable. | 07:14 |
| pvuorela | dcaliste: then the porting would probably go removing the "after" usage but still using ExtendedStorage. and after that from ExtendedStorage to other storage type. | 07:14 |
| dcaliste | Exactly. That's my plan. | 07:14 |
| dcaliste | After everything settle a bit in mKCal (and ExtendedStorage is still in), I'll do a PR in Google Buteo plugin to remove after usage but still using ExtendedStorage. | 07:15 |
| pvuorela | also, we'll need to do eas for those. | 07:16 |
| *** rdr_ is now known as rdr | 07:16 | |
| dcaliste | If everything goes fine, there will be a second PR to drop ExtendedStorage usage. If it's creating issues, there will still be time to add 'after' support in the new API. | 07:16 |
| dcaliste | Sadly this plan implies more work from your side to adjust EAS plugin also… | 07:17 |
| dcaliste | If it's too much of a burden, we can keep the 'after' argument for sure (maybe in a separated routine). | 07:18 |
| pvuorela | i'm still thinking there could be some guessing whether it's not useful in the end. if comparing calendar data to remote content, it could still be an optimization to skip comparisons on guaranteed in-sync events. | 07:21 |
| dcaliste | Indeed, it's an optimisation. But do you call 'allIncidences()' in EAS pkugin ? Because calling it kills any optimisation since it's loading in memory all incidences anyway. So listing one or two deleted incidences in addition will make no difference. | 07:26 |
| dcaliste | See current status of Google plugin for instance in googlecalendarsyncadaptor.cpp#1688. | 07:27 |
| pvuorela | no allIncidences() in eas. but besides optimization on mkcal, it can be an optimization also on the sync side, maybe even more of that. | 07:29 |
| dcaliste | Ok, so in EAS, you're doing it in an optimized way, just listing the difference (with the risk of missing something depending how the sync date is set). To keep it like that, I'll add routines in the backend with qdate arguments. | 07:31 |
| pvuorela | the eas gets modified etc lists based on the after parameter. didn't yet figure out how easily it could be switched to compare everything, quite a bunch of code on that side too. | 07:33 |
| dcaliste | Yes, I understand. So let's be a bit conservative in that matter. I'll add support routines in the backend and propagate them in the new CalendarStorage class also. | 07:35 |
| pvuorela | alright, thanks. | 07:35 |
| dcaliste | About the alarm handling, I've created a dedicated PR since it's not relying on any SQLite changes, see mkcal#65. | 07:39 |
| dcaliste | As I tried to explain in the PR message, the rational came from the necessity to add the Notebook uid argument and also to have a way to get the instances() of a recurring event. | 07:39 |
| dcaliste | But this ends up in a partial rework on how alarms are handled, moving to a per series instead of a per incidence treatment. | 07:40 |
| dcaliste | This avoid to treat cases like, if an exception is modified, check that its parent is also, or add it to the list of modified inciences. | 07:41 |
| dcaliste | Like that, you can call the setupAlarm() routine on the added + modified + deleted list, without paying attention of recurring and exceptions. | 07:42 |
| pvuorela | yeah. i'll keep on checking that. needs a bit of extra care since it's both moving and adjusting the code :) | 07:43 |
| dcaliste | Yeh :/ | 07:43 |
| dcaliste | At least, PR#60 and PR#61 are becoming more and more like simple addition of new classes. | 07:44 |
| pvuorela | that's good indeed. | 07:45 |
| dcaliste | By the way, more a strategical question: in a while, after all of this API changes settle down, what do you think of the possibility to add KCalendarCore+mKCal as allowed libraries in harbour ? | 07:48 |
| pvuorela | hm, not totally out of the question if we get the api on satisfactory level and we're sure enough of it. might also need some work on the permissions, but let's see. | 07:51 |
| pvuorela | then for another thing, i'm not having a long weekend off for midsummer and then on july there's the vacation time coming up. we could have a meeting still next week, but maybe some break after that. | 07:52 |
| dcaliste | Ok, thanks for the answer on harbour question. Looks good. About summer break, sure. Myself, I'll be off the first week of July, and then, the last of July and the first of August. We can have a meeting next week and then enjoy vacation time ! | 07:56 |
| pvuorela | sounds like a plan :) | 07:56 |
| dcaliste | Ok, thanks pvuorela for the discussion this morning. I'll add the missing routines in mkcal#60 today or in the coming days. | 08:05 |
| pvuorela | thanks. | 08:06 |
| *** ilpianista is now known as Guest3583 | 10:13 | |
| akrosi | had a thought about VoLTE on Verizon on the Xperia 10 III. The newer supported Xperias don't support CDMA, and the last test recorded on the provider chart at https://forum.sailfishos.org/t/volte-provider-support/11501 is in mid-2022, before the sunsetting of Verizon's 3G network. At the time, initiating a VoLTE call may have required negotiating through the CDMA 3G network... which the Xperia doesn't support. | 14:57 |
| akrosi | All speculation, but I'm interested in seeing if I can coax it into working without changing carriers :) is VoLTE available without buying a license now, or is it still in beta? | 14:58 |
| henk | I’m trying to install "Maliit Presage Plugin" via chum-gui but it gives some error message I don’t understand: »the installed libpresage-someversion requires 'presage-data', but this requirement cannot be provided«. the package "Presage Data" is installed, though. any advice how to get more info to figure out what’s wrong? | 19:10 |
| mal | try refreshing the repo | 19:17 |
| henk | mal: done, no change | 19:23 |
| mal | is the package installed? | 19:31 |
| henk | mal: no, doesn’t show as installed in chum-gui at least | 19:35 |
| mal | I meant from commandline | 19:36 |
| henk | hmm, I never know what the right tool is … pkcon? zypper? rpm directly? | 19:37 |
| mal | pkcon or zypper | 19:37 |
| henk | hm, haven’t found the right pkcon command to see that yet but this seems interesting: there are two maliit-presage-plugin packages, for different architectures it seems: http://ix.io/4yHL | 19:40 |
| henk | »pkcon get-packages | grep presage«: http://ix.io/4yHM | 19:41 |
| henk | no, this particular package is not installed but other presage packages are. I thought the whole list with 'presage' might be interesting as well for this issue, so I didn’t grep for that particular package but a bit wider … | 19:42 |
| mal | so installing for example "Presage English US" from gui app doesn't work? | 19:43 |
| henk | mal: incorrect, that package is installed, as is the one for german. installing "Maliit Presage Plugin" (or "maliit-plugin-presage-1.2.1-1.2.1.jolla.aarch64", I guess) fails. | 19:45 |
| henk | I guess I should try with pkcon? | 19:45 |
| henk | http://ix.io/4yHN | 19:46 |
| henk | installing presage-data: http://ix.io/4yHO | 19:47 |
| henk | Fatal error: presage-data-2.0.0-1.2.1.jolla.aarch64 is already installed | 19:47 |
| mal | no idea why that happens | 20:31 |
| henk | http://ix.io/4yHT ¯\_(ツ)_/¯ oh well, that worked | 20:35 |
| mal | hmm | 20:36 |
| attah | something-something vendors | 20:37 |
| mal | could be | 20:38 |
| henk | vendors? | 20:38 |
| attah | henk: what you mistakenly called architectures above | 20:39 |
| henk | ah | 20:40 |
| henk | it seems to me like the "maliit" and the "keyboard-presage" packages belong together and the "presage", "presage-data" and "presage-lang" packages and their "provides" and "requires" collide … | 20:41 |
| henk | oh, the former are version 1.2, the latter version 2.0. maybe | 20:43 |
| henk | the pkcon error messages are crap o_O | 20:43 |
| henk | »Fatal error: the to be installed presage-2.0.0-1.2.1.jolla.aarch64 requires 'libpresage1', but this requirement cannot be provided« | 20:44 |
| henk | anyway: now the presage keyboard variants show up in the settings but selecting them does not cause them to be available in 'messages' … when I enable only presage variants, I get an empty field where the keyboard should be o_O | 20:47 |
| henk | when I enable one non-presage keyboard, that’s the only one available | 20:48 |
| Mister_Magister | Let's play a game! Anyone who guesses first why sfos is not able to decode dts gets absolutely nothing! | 20:53 |
| Mister_Magister | that's right! Licenses! | 20:54 |
| henk | mal: it works for you, right? could you run 'pkcon get-packages | grep presage'? | 20:56 |
| mal | henk: only keyboard-presage-en_US, maliit-plugin-presage and presage-lang-en_US | 21:34 |
| henk | weird, almost same here, but also with de_DE variants … | 21:50 |
| mal | I also have the finnish versions installed but that was not relevant so I skipped it | 21:55 |
| mal | and you have the keyboard enabled in the settings? | 21:56 |
| mal | and the normal keyboards if you want those | 21:56 |
| b100dian[m] | Mister_Magister: device trees? | 21:57 |
| Mister_Magister | b100dian[m]: what | 21:57 |
| Mister_Magister | no boooo | 21:57 |
| Mister_Magister | nobody does hw audio decoding | 21:57 |
| b100dian[m] | Ah, gotcha | 21:58 |
| Mister_Magister | lol was doing something in gstreamer and found solution in… lipstick? | 21:59 |
| Mister_Magister | what a coincidence | 21:59 |
| henk | mal: yeah. when I enable only the presage variant, I get only a blank blue area where the keyboard should be. when I enable a "normal" and a presage, I only get the "normal" variant and switching by holding the spacekey doesn’t show a selection. when I enable german and english "normal", as well as a presage variant, I only get the two "normal" keyboards for selection. | 22:11 |
| mal | henk: wondering how you manage to break things | 22:53 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!