Storage of the per-calender configuration
Implement *storage* of per-calendar options outside of the included calendar file. Use cases: included ics calendar file (no place for options), included shared calendar (many users include this calendar and want to see it in different color), read-only included calendar.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Two possibilities.
First approach: in a proxy calendar file
main calendar includes a secondary calendar.
secondary calendar specifies all options and either contains the data or includes another calendar file with the data.
It will need calendar options like
Disabled [0]
ReadOnly [0]
NoAlarms [0]
Color [Red]
DefaultHilite [Always]
DefaultTimezone [America/
in the beginning of calendar file.
The point is that "another calendar" can be shared and different users may want different options. Or another calendar may be ics file, and these "options" cannot go there at all.
The problem - recursive includes, as a concept, are very foreign to ical,
they'll be difficult to implement and will require changes in gui and tcl
bindings.
Second approach: In the main calendar Include directive:
- IncludeCalendar [/home/
+ IncludeCalendar [/home/
+ Disabled ReadOnly NoAlarms
+ Color [Red]
+ Hilite [Always]
+ Timezone [America/
+ ]
problems - options are lost when a calendar is removed from ical, will still
need per-calendar options as in the first approach (for the "main" calendar)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
