Ahh, you beat me to it. I was just about to summarize our chat on irc
about this.
So some questions Priscilla and I had about this:
1. What's the success / failure rate on this? Priscilla mentioned she
had problems getting Newsreader to do the right thing on her Mac. If
it fails, how do we fail elegantly?
2. Will the right thing happen with Apple iCal from both Safari and
Firefox?
So, in a world where subscribe happens automagically, reliably, the
workflow would be something like...
1. Subscribe with Chandler
2. Subscribe with Apple iCal
3. Subscribe with feed reader
4. Download calendar and tasks*
* I'm wondering if Export data to desktop is a tad too techie and
maybe confusing because the CC isn't actually looking at their
personal calendar and doesn't really think of Cosmo UI as their
personal calendar app.
1. --> Instructions for how to Subscribe with Chandler
2. --> Launches Apple iCal to subscribe;
{If user does not have iCal, pop-up: Apple iCal cannot be found. Try
importing the calendar and tasks to your calendar application by
downloading to the desktop. [Cancel] [Okay]}
3. --> Launches feed reader to subscribe
4. --> Downloads .ics file to Desktop
If 2 or 3 fails...then we would need to pop-up the dialog with the
URLs...
Does this sound right?
=====
In the future, when we're ready to support a broader range of apps,
we can instead have...
1. Add to Chandler
2. Add to calendar application
3. Add to feed reader
1. --> Instructions for how to Subscribe with Chandler
2. --> User selects from a list of apps.
* If they select an app that support webcal, we auto-launch the
app and subscribe.
* If they select an app that doesn't support webcal, we suggest
that they download and import.
3. --> Launches feed reader to subscribe.
Thx, Mimi
On Dec 11, 2006, at 1:01 PM, Brian Moseley wrote:
On 12/11/06, Priscilla Chung <[EMAIL PROTECTED]> wrote:
I updated mock-ups on the subscribe workflow (2 new workflows).
I'm hoping
to have more details written up in the spec, but I think this
covers most of
the discussion. LMK if you see anything that is jarringly wrong.
there's no technical need to open the collection details dialog when
the user chooses a subscription method.
when a method is chosen, the client can call back to the server, and
the server can send the appropriate response that directs the browser
to open ical or handle the atom feed (or causes the browser to ask the
user to save the file).
ps: we don't support rss! we need to stop using that term.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
