see in-line...
On Dec 12, 2006, at 7:58 AM, Brian Moseley wrote:
On 12/11/06, Mimi Yin <[EMAIL PROTECTED]> wrote:
So, correct me if I'm wrong. We could get rid of the 'Download .ics'
option completely and just have a n 'Subscribe with calendar
application' option. If Subscribe fails because the user's calendar
app doesn't support webcal, they can at least download the calendar
to their desktop?
i get the feeling that you're expecting "if subscribe fails, then xxx"
to all happen in one step, but it can't.
so let's say the user chooses to "subscribe with calendar app". this
causes the browser to pop up a dialog with two options: 1) choose an
application to handle files of type text/calendar or 2) save the file
to disk. if the user chooses an application, the browser opens the
application, hands it the file, and ducks out of the way. it has no
way of knowing if the application can do anything with the file, and
the application can't tell the browser anything. so there's no way for
the browser to give the user a fallback option.
i think this means that we probably still need an explicit ics
download option.
ic the options 1 and 2 are offered simultaneously. okay.
I think even if the browser is handling the workflow for
subscribe...we want to provide CC's with access to the URLs. That
means we would want to give them access to the same Collection
Details dialog that users can see when they're logged in.
how, specifically?
do you mean how, as in how would it look in the UI? I think we can
have the same little blue 'i' circle next to the collection name as
we do when the user is logged in.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
