2 ms·
I was thinking about this on the way to work earlier regarding calendars, and how I don't want to choose a particular service to grace with my data, and then tr
by jodrellblank 18y ago
I was thinking about this on the way to work earlier regarding calendars, and how I don't want to choose a particular service to grace with my data, and then try to hack 'sync' to other services and devices.
I came up with...
Make the data the important part. Carry the data structure around with me on my device(s) of choice.
Have the data accessible in a standard format - i.e. I can keep it in vCal/vCard format - or, in any format I choose as long as it has an included vCal/vCard interpretive layer.
Anywhere I want to use it, it would be up to the program to read/write the appropriate format. That is, instead of a proprietary data store with export/import as afterthoughts, it would be fundamental - or so key that it would cease to exist in its own right. You don't import wood into a chisel in order to shape the wood, why must we import all of our calendar into a program in order to add an appointment?
The model I was thinking of would be more like the wood carving example - you'd present a slice of your calendar to a program, which would carve it and give it back.
Still plenty of details that would need working out, though.