Re: [Evolution-hackers] (summarize ][) New 'eclient' branch in eds

[Patrick Ohly <patrick ohly gmx de>]

On Mo, 2011-05-09 at 17:00 +0200, Milan Crha wrote:
> On Wed, 2011-05-04 at 14:37 +0200, Milan Crha wrote:
> > So here left basically three things,
> >    a) merging some API in utils,
> >    b) getting well-known properties,
> >    c) setting well-known properties 
> 
> 	Hi,
> I just did a commit into the eclient branch with a fix for b) and c).
> There is a little change, I named those functions:
>    e_client_get_backend_property_sync
>    e_client_set_backend_property_sync
> with their async versions too.
> 
> Well-known properties are:
>   * for a book:
> 	BOOK_BACKEND_PROPERTY_LOADED
> 	BOOK_BACKEND_PROPERTY_ONLINE
> 	BOOK_BACKEND_PROPERTY_READONLY
> 	BOOK_BACKEND_PROPERTY_CACHE_DIR
> 	BOOK_BACKEND_PROPERTY_CAPABILITIES
> 	BOOK_BACKEND_PROPERTY_REQUIRED_FIELDS
> 	BOOK_BACKEND_PROPERTY_SUPPORTED_FIELDS
> 	BOOK_BACKEND_PROPERTY_SUPPORTED_AUTH_METHODS
> 
>    * for a calendar:
> 	CAL_BACKEND_PROPERTY_LOADED
> 	CAL_BACKEND_PROPERTY_ONLINE
> 	CAL_BACKEND_PROPERTY_READONLY
> 	CAL_BACKEND_PROPERTY_CACHE_DIR
> 	CAL_BACKEND_PROPERTY_CAPABILITIES
> 	CAL_BACKEND_PROPERTY_CAL_EMAIL_ADDRESS
> 	CAL_BACKEND_PROPERTY_ALARM_EMAIL_ADDRESS
> 	CAL_BACKEND_PROPERTY_DEFAULT_OBJECT

Why duplicate the LOADED/ONLINE/READONLY/CACHE_DIR/CAPABILITIES
properties? They could be defined as common E_CLIENT_BACKEND_
properties.

-- 
Bye, Patrick Ohly
--  
Patrick Ohly gmx de
http://www.estamos.de/