[dev] time object api vs. ics

[Jan Schneider]

Zitat von Chuck Hagenbuch <chuck at horde.org>:

> Quoting Jan Schneider <jan at horde.org>:
>
>>> Exactly - same thing as I might want to see only some of my tasklists
>>> on my calendar. Right now the tasklists that show up on the calendar
>>> are affected by my display choices in Nag - not good.
>>
>> This still could be done by a thing like Whups' listTimeCategories().
>
> That's a possibility, but it doesn't really offer the flexibility that
> individually defined .ics calendars do. For example, what if I only
> wanted to see tickets from a specific queue on the calendar? And in
> Nag, the options are by tasklist, by completed/future/incomplete/all,
> and any combination of those (you could throw in category too, perhaps).
>
> Thinking about this it seems like we need an internal calendar
> browser, not just a select box. "What do you want on your calendar: "
> ... list of applications, then each application can describe its
> time-object-like-things in a way appropriate for that application.

Yeah, but this kind of fine granularity has nothing to do with the  
transport protocol of the actual data. Such a browser could be created  
nicely from a listTimeCategories() output.

Of course, nothing speaks against making listTimeObjects() output  
available externally through ics.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/