109
edits
(update headings) |
m (typo implemantations) |
||
| Line 13: | Line 13: | ||
== Points to remember == | == Points to remember == | ||
The different storage types will be created using different | The different storage types will be created using different implementations of the calICalendar interface. So far so good. The network is where the problems come. You don't want a different implementations just because the data file is stored in a different place. | ||
Also, it should be possible to mark a certain calendar for offline use. If marked, calendar should download the events to a local file. Then it needs to sync when coming online again. Thoe code to do this should be shared for all different calendar types. | Also, it should be possible to mark a certain calendar for offline use. If marked, calendar should download the events to a local file. Then it needs to sync when coming online again. Thoe code to do this should be shared for all different calendar types. | ||
edits