[dev] Subscribing to external calendars provided by Horde Apps Re: Custom colors and subscribe-options for calendars provided by Api

[Jan Schneider]

Zitat von Ralf Lang <lang at b1-systems.de>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 25.03.2013 09:41, Karim Geiger wrote:
>> Hi guys,
>>
>> I just wanted to add a custom color and the possibility to
>> subscribe to an calendar provided by my horde application.
>>
>> The app itself returns an array in the listTimeObjectCategories
>> function provided in the Api.php-file.
>>
>
> Hi List,
>
> Karim wants to expose an external calendar provided by a horde app
> (like whups) as a calendar on the rpc interface (browse).
>
> External Calendars can be "exported" in the traditional interface but
> cannot be subscribed to/offered via RPC.
>
> Currently browse() only implements internal calendars.
>
> I first searched for them under -system- and then under the user uid
> because Kronolith_Calendar items default to the user uid
>
> External calendars have a multipart calendar id consisting of
> external_$api/$shareid and do not match the way
> Kronolith_Api::browse() handles resource paths.
>
> When implementing browse() for external calendars, which route should
> be taken to be best accepted upstream?
>
> 1) Putting them under -system-
> 2) Putting them under $user/-external-/$api/$shareid
> 3) Putting them under $user/-external_$api-/$shareid
> 4) None of that. Each App which wants to provide vcalendar data must
> implement an own interface instead.

4 makes most sense to me and is how we already deal with this in Nag.
-- 
Jan Schneider
The Horde Project
http://www.horde.org/