[Tickets #1650] Add turba preference to set which addressbooks to display
bugs@bugs.horde.org
bugs at bugs.horde.org
Wed Jun 8 19:35:45 PDT 2005
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/?id=1650
-----------------------------------------------------------------------
Ticket | 1650
Updated By | kevin_myer at iu13.org
Summary | Add turba preference to set which addressbooks to display
Queue | Turba
Version | 2.0.2
State | Feedback
Priority | 1. Low
Type | Enhancement
Owners |
-----------------------------------------------------------------------
kevin_myer at iu13.org (2005-06-08 19:35) wrote:
>
> Logically this makes sense to me. Unfortunately it's also a
> compatibility break with the possibility to be very subtle and
> annoying. I think what you should do, and even perhaps what we should
> do by default or recommend, is to lock the existing preferences in
> IMP and Kronolith and use a preferences hook to retrieve the Turba
> default_dir value when those prefs are requested.
Exactly what I had just typed out before I tried to use the non-existent
Tabbed Browsing feature of Whups to reference back to your comment and lost
it all :)
Even though you do that, you still have the issue that your 'add_source' in
IMP is weighted higher than the order you've selcted for 'addressbooks' in
Turba. In my mind, add_source is only defining which addressbook you want
to save addresses to and it should not be the default selection. In fact,
you may not even have it selected as an addressbook to display. The first
addressbook in the Turba 'addressbooks' option should be selected. That's
what users expect, because I had configured localsql to be first and
_everyone_ wanted our main directory first in Turba. And they want that in
IMP too. Thats also where the idea that all Address Book related stuff
should be set in Turba and then the only option set within each module that
uses Turba would be exactly how the data made available from those sources
is used (like what fields to search, for IMP). I myself thought that the
address books selected in IMP controlled what showed up in the Address Book
available from the IMP compose screen but they only control name expansion
functions.
> Think we can resolve this ticket?
Sure, every ticket is resolvable with enough resources. Oh, you mean was
the original spirit of the ticket resolved? If IMP's contacts screen
behaves properly, I'd say yes. ;)
More information about the bugs
mailing list