[Tickets #2245] Horde Share implementation for Turba

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://dev.horde.org/horde/whups/ticket/?id=2245
-----------------------------------------------------------------------
 Ticket             | 2245
 Updated By         | Jan Schneider <jan at horde.org>
 Summary            | Horde Share implementation for Turba
 Queue              | Turba
 Version            | HEAD
 State              | Feedback
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | Michael Rubinsky
-----------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2005-08-22 00:26) wrote:

>> I don't understand what the display_type is for, and the explanation
>> in sources.php doesn't help much either.
>
> This was meant as a 'user friendly' name for the source type.  For 
> example, on the 'My Addressbooks' page, the user can create a new 
> addressbook and must choose what type (source/backend - whatever you 
> want to call it) of addressbook to create.  I thought that "localsql" 
> might not be user friendly enough.  The display_type (I guess not the 
> best name for this attribute) setting  holds the title that wi

Does it really make sense to allow the users to create shared address books
for more than one backend? Most of them probably don't even know what a
backend is. It would make more sense to me if there is only one backend
providing the ability to share address books. Maybe through a configuration
option, like the client backend?