FossifyOrg
Implementing color-data to ICS import / export for events (part of RFC 7986)
Checklist
- [X] I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- [X] I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- [X] I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- [X] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- [X] This issue contains only one feature request.
- [X] I have read and understood the contribution guidelines.
- [X] I optionally donated to support the Fossify mission.
Feature description
It would be awesome to also include color information for events or tasks within an export- / importable ICS file. With this feature we could use the import / export feature to transport color-coded events between different calendars. Also it would be one step into implementing 'New Properties for iCalendar' - RFC 7986.
Why do you want this feature?
- Improved migration between calendars
- beeing able to store color-data for backups
- future-proofing / implementing of updated RFC 7986
Current Situation:
(Google Calendar - GC; Fossify Calendar - FC)
GC's ICS-export does NOT include color-data for events as they are holding on to RFC5545, which does not specify the need for encoded color data in e.g. events, although they are using color in their own applications.
This flaw and need occured to me as I am currently trying to transfer all my carefully color-coded GC events into my Nextcloud instance via 'DAVx^5' and FC. I am able to view the color-coded events stored in GC on my phone via FC with their appropriate colors without issue, as long as FC is accessing them via the phones internal calendar management (as far as I've understood). With FC beeing able to parse the color data in the GC events (also beeing the only tool known to me 💪) it would be INSANELY USEFUL to also export them with the color data in a standardized manner (which is part of the 'New Properties for iCalendar' - RFC 7986). They should be able to be imported whilke retaining the color-data as well into other event-types / calendars.
Additional information
A sketch of what i had in mind including my scenario.
This hopefully clears a few things up.
Smart workaround! Was looking around since I couldn't believe this behemoth of a company hasn't even integrated RFC 7986 for what's arguably one of the most critical features on GCal.
[insert nice sketch here] Value is CSS3 color name
There is just one problem:
The colors used by GC aren't there in https://www.w3.org/TR/css-color-3/#svg-color. We can choose to work around it by finding the closest named color.
We can choose to work around it by finding the closest named color.
We did that. Simple euclidean measure but it's good enough.