On 7/12/06, Sheila Mooney <[EMAIL PROTECTED]> wrote:
1) If a Chandler desktop client user deletes their repository and runs Chandler again, they would like to have a way to reconstruct their sharing world to what it what previously. What should be the user experience for this? I will post a new thread and send to the design list.
restore from backup :)
2) For Chandler web client users, what shares do you actually see when you log into Scooby - and how does Scooby get that information? I believe Morgen has a number of questions around this specifically. I will post this thread to the Scooby list.
scooby looks in your cosmo home directory for whatever calendars are stored there.
In the context of these 2 different problems, users may have published and subscribed to shares on different servers. My feeling is that in the beta timeframe 90% of the use cases will involve people using our hosted service running Cosmo. In some cases people will be using multiple servers but it won't be as common. I think we should keep this in context as we explore ideas/solutions to the above 2 issues.
1) cosmo and scooby don't have the notion of "subscribing to a remote calendar". scooby simply displays whatever calendars are stored in the cosmo home directory. 2) chandler has no way to tell cosmo that chandler has subscribed to a remote calendar. the only thing chandler can do is copy the content of the remote calendar into its local repository and then sync a coppy of that content into cosmo. at that point the data in cosmo, the data in chandler, and the data in the origin calendar server are all copies of each other. it would be a lot nicer if chandler could just tell cosmo to subscribe itself to remote calendars, at least with regard to syncing. the down side is that if either cosmo or chandler has updated its subscription more recently than the other, the data you see in scooby and chandler could be slightly different. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
