Re: Re: [Chandler-dev] Subscribe/Publish of CalDAV collections

Are we going to go ahead and make this change for Preview. I couldn't  
find a bug logged on this.

On Jun 26, 2007, at 6:39 PM, Mimi Yin wrote:

> Replying to this thread on the design list.
>
> Mikeal,  can we subscribe to a CALDAV url today in Chandler Desktop  
> without filling out a sharing account? (I thought we could.)
>
> Morgen, could we have a 'CalDAV' option in the Sharing account  
> pulldown? It wouldn't really be an account pulldown anymore...We  
> could rename Sharing account to be Share via: or Share with: (This  
> sounds like post-preview work.)
>
> I think I'm less worried about the terminology. Chandler has a lot  
> more functionality than a Calendar client so I don't think our menu  
> structure can be (expected to be) the same. I'm betting that for  
> most people, 'Share' will be a more discoverable place to find  
> subscribing and publishing than Collection or Calendar even.
>
> Mimi
>
> On Jun 19, 2007, at 7:09 PM, Katie Capps Parlante wrote:
>
>> Mimi, do you have thoughts about Mikeal's proposal?
>>
>> If we come to an agreement on a change, can we create a task and  
>> SWAG it?
>>
>> The current plan of record is to focus on interop in 0.7.1,  
>> scheduling CalDAV related changes for that time frame would be  
>> appropriate.
>>
>> Cheers,
>> Katie
>>
>> Morgen Sagen wrote:
>>> On May 7, 2007, at 3:40 PM, Mikeal Rogers wrote:
>>>> Our experience right now when subscribing and publishing from  
>>>> other CalDAV servers is pretty poor.
>>>>
>>>> - We only support "sharing" and a "sharing" account. This is not  
>>>> only alien to most CalDAV users it doesn't follow normal  
>>>> subscribe/publish workflows from other clients.
>>>> - For every server that requires auth we need to add an  
>>>> "account" in the account preferences.
>>>> - All of our current account options refer to "sharing", this in  
>>>> contrast with language used in all other calendar clients. In  
>>>> addition these options don't just publish the events in a  
>>>> calendar they put the old chandler xml file up there and try to  
>>>> publish more than just calendar data.
>>>>
>>>> In most clients you simply select "subscribe" or "publish" on  
>>>> your calendar collection and are prompted to enter a URL. The  
>>>> client attempts to publish and if the server requires auth it  
>>>> prompts you for auth.
>>>>
>>>> Obviously this is in contrast to our current sharing workflows  
>>>> and we're getting close to release. In the interest of keeping  
>>>> this simple and nice for everyone I'd like to suggest a new  
>>>> "Publish to CalDAV" and "Subscribe to CalDAV" option in either  
>>>> the Collection menu or the Share menu that would follow the  
>>>> simpler usage described above that is being implemented across  
>>>> every other calendaring client. It would be great to have this  
>>>> in a released Chandler before the end of the summer as the  
>>>> abundance of caldav servers and clients is about to increase  
>>>> dramatically, obviously only if it's not too much work/effort to  
>>>> risk our Preview schedule.
>>>>
>>>> -Mikeal
>>> I agree with pretty much everything you said, but I don't know  
>>> how much of this can be done for Preview.
>>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>> Open Source Applications Foundation "chandler-dev" mailing list
>>> http://lists.osafoundation.org/mailman/listinfo/chandler-dev
>>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> 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