[chandler-users] Tasks with Start/End <--> Chandler Starred Events

[William K. Volkman]

Hi Mimi,
On Mon, 2008-05-19 at 13:04, Mimi Yin wrote:
> Hi,
> 
> For those of you syncing Chandler with another calendar application,
> do you have a preference when it comes to how to reconcile Chandler
> "starred events" and the notion of "tasks with start and end
> date/times" in other calendar apps?
> 
> In other words, when syncing with other calendar apps, would you
> prefer to see "starred events" on the calendar? or would you prefer to
> see them as tasks with start and end date/times?

Tasks need to remain as tasks, and having them show up as events would
be really annoying (starred or not).  And I've already complained about
the replacement of tasks in chandler with "starred".

I didn't get the chance to respond to your reply to me.  IIRC we agree
that "tasks" are something that have "heft" to them.  I did want to
point out that your user demographic that drove this change is most
likely biased.  I don't think that a lot of the people who have a
driving need for this level of organization are going to be using an
"evolving" system, and thus you would be getting a disproportionate
number of people unsure what the difference is between and item and a
task.

My $0.02,
William.


> 
> Mimi
> Begin forwarded message:
> > From: Randy Letness <randy at osafoundation.org>
> > Date: May 19, 2008 9:32:53 AM PDT
> > To: Chandler Server <cosmo-dev at lists.osafoundation.org>
> > Subject: Re: [cosmo-dev] caldav<-->chandler model
> > Reply-To: Chandler Server <cosmo-dev at lists.osafoundation.org>
> > 
> > Mimi Yin wrote:
> > > Hi Randy,
> > > 
> > > I think we want anything with EventStamp to -->VEVENT. Meaning,
> > > user's calendar in Chandler should look the same as calendar in
> > > other apps.
> > > 
> > > Rest of proposal looks good.
> > > 
> > > Mimi
> > 
> > 
> > The problem is that VTODOs can have event info too.  So the question
> > is do we pull that info into chandler (EventStamp) where it can be
> > changed and exported back as a VTODO, or do we just want to import
> > the item as an "event" that will be exported as a VEVENT the next
> > time the caldav client syncs.  That would mean every VTODO with date
> > info would be transformed into a VEVENT, which will probably confuse
> > clients.
> > 
> > -Randy
> > _______________________________________________
> > cosmo-dev mailing list
> > cosmo-dev at lists.osafoundation.org
> > http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
> 
> 
> 
> ______________________________________________________________________
> _______________________________________________
> chandler-users mailing list
> chandler-users at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/chandler-users