Calendar syncing

[Foxite]

There is a calendar branch in this repository, what kind of state is it in? I don't know enough c++ to tell what parts are incomplete, but it definitely looks like it's behind on a major restructuring of the codebase.

What would it take to update the current calendar branch and finish it? I am ready to test my additions to AsteroidOSSync (AsteroidOSSync#89) but of course, that's kinda hard when my watch doesn't support it.

[Foxite]

I've had a closer look and it looks like there is no "major restructuring" apart from moving everything into a src folder after porting it to cmake.

I've attempted to copy the changes from the calendar-test branch to master, the result of which is here

Since two new dependencies were added, I've had to add cmake files for that here

Both of these are very much cargo-cult attempts at getting it to work, derived from existing code, because I don't know c++ or cmake.

It compiles, but I was unable to tell if it works when you install it on a smartwatch, because my AsteroidOSSync branch doesn't seem to be able to connect, and there are no log messages. I don't know if I correctly built an ipk file, I was unable to find out how to do this.

If anyone can point me at the relevant documentation, that would be a great help!

[beroset]

Possibly related: AsteroidOS/asteroid#221

[Noodlez1232]

Hi! I'd love to get started on this, but I am interested on exactly how the importing happens on the watch. I want to get this ability added into Gadgetbridge since I'm working on updating the current implementation there (It's been 9 months since I pushed the initial and I haven't touched it since).

[beroset]

Importing a calendar on the watch uses icalconverter, so to import a calendar, one could use icalconverter import -d my.ics. The import says to import, of course, and the -d flag tells it to delete all existing calendar entries before importing. Looking at the code for icalconverter which is in the nemo-qml-plugin-calendar package might be helpful.