I think you missed my point. I am not talking about a shared collection from some Chandler user. I am talking about subscribing to one of the many of hundreds (or more) of Google and iCal calendars available publicly on the internet. Since these are not "shared" in our sense of having bilateral read/write access they show up in my Chandler as Read Only subscriptions. I will never be able to modify the original Google Calendar or iCal events on the public server. But I do want to integrate these events into my own personal calendars in such a way that I can modify the start/end times, change the date, set alarms, annotate them with notes, stamp them as tasks or messages, etc. All without having to manually copy or recreate each event in one of my own calendars.
Pieter On 5/10/07, Jeffrey Harris <[EMAIL PROTECTED]> wrote:
Hi Pieter, > As a Read Only collection I do not have the option to publish these > events to my account on Chandler Server. But since my Dashboard is > published, I can add these events to my Dashboard and then are > available on the server. It's a bug that you can't move items from a read-only collection to other collections in the calendar. In the table view, you should be able to. So it's not just the Dashboard, you can put read-only events anywhere. > I find the ability to import public event calendars like baseball > schedules, opera schedules, club schedules, PTA/school schedules, > etc. into my own calendar, and have the ability to modify the events > and annotate them, and to have these on my Chandler Server account to > be incredibly useful. Annotation (of read-only or read-write items), is a feature that isn't going to make it in for Preview. But I agree this would be valuable. > I hope that in the interests of security there will be some process > by which this functionality can be preserved. (For example, if I > export a Read Only collection as an .ics file) then delete the > collection from Chandler and then import it into Chandler does it > become Read Write or is the Read Only bit still preserved through the > export/import process) For preview, read-only won't have much weight (in a security sense). If you share your data read-only with other people, they'll be able to edit it if they try hard. When people talk about using ACLs on Cosmo, this is one of the major things ACLs would try to fix. I think it would be a lot of work, though (at least on the desktop side), and it's not clear how important strong security is to our target users. Reasonable people have respectfully disagreed on this topic, repeatedly, so I for one am very much looking forward to seeing who adopts Preview and asking them how important this is then. Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
