[dev] [cvs] commit: incubator/minerva/lib Outcomes.php Recurrence.php api.php incubator/minerva/locale/sl_SI/LC_MESSAGES minerva.mo incubator/minerva/outcome ics.php list.php topay.php incubator/minerva/po minerva.pot sl_SI.po incubator/minerva/recurrence ics.php list.php ...

[Jan Schneider]

Zitat von Duck <duck at obala.net>:

> duck        2007-05-26 06:51:16 EDT
>
>   Modified files:
>     minerva/lib          Outcomes.php Recurrence.php api.php
>     minerva/locale/sl_SI/LC_MESSAGES minerva.mo
>     minerva/outcome      list.php topay.php
>     minerva/po           minerva.pot sl_SI.po
>     minerva/recurrence   list.php
>     minerva/templates/outcome list.html
>     minerva/templates/recurrence list.html
>   Added files:
>     minerva/outcome      ics.php
>     minerva/recurrence   ics.php
>   Log:
>   Replace  listTimeObect api call with dedicated ics files. Can be  
> directly added to calendars using new subscribe/un subscribe  
> Kronolith call.

This doesn't make any sense. Why would you want to convert invoices to  
dates to ics data, transport it over http and convert it back to  
events, if you can pass them directly to Kronolith?
Horde apps use the internal api, anything else adds unnecessary  
overhead. Remote calendars are really for remote calendars, ie.  
anything not on the same Horde install.
Of course you can still offer an external ics interface if you see any  
purpose for that, but please revert the replacement of the internal api.

Jan.

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