[turba] What is the status of Turba (contact fields) ?
Michael Rubinsky
mrubinsk at horde.org
Tue Dec 8 19:49:58 UTC 2009
Quoting Rolf Gloor <thunderbird at glr.ch>:
>>>
>>> => So the better the compatibility with MS Outlook, the more people
>>> will actually use Horde, the broader Horde will be installed and the
>>> larger the market share will get.
>>>
>>> So please make sure, that the default is good enough to cover the
>>> (compatibility) needs for the majority.
>>
>> So you need also to include the schema used in Thunderbird, Apple-Mail
>> and maybe Notes for Business-Users??
>> As they are also incompatibel with each other this is not possible at
>> all so you have to decide for your own. Horde/Turba is not a Oulook
>> extension and to break things for others to be compatible with Outlook
>> is not really useful.
>>
>>
>>
>> Regards
>>
>> Andreas
>>
>
> Hi Andreas
>
> Thanks for your response.
>
> I do understand your comments and concerns.
>
> However, the basic set of fields is pretty limited.
>
> Even when not supporting all above mentioned:
>
> => Extending the basic sets to somewhat more useful (less limited),
> would greatly improve the situation.
>
> Here some proposals:
>
> - a third address set 'other' (beside 'home' and 'work')
> - at least 2 more eMail addresses ('email2', 'email3')
> - many more phone numbers ('workphone2', 'homephone2', 'workfax',
> 'homefax', 'other', ...)
> - more urls ('homeurl', 'workurl')
These are all very simple for the horde administrator to add.
> - and eventually the default eMail and address (to use if not
> specified, don't know the correct wording for it)
>
> The naming of the fields above are just kind of top of my head and
> might need some tweeking to fit the standard.
>
> However, those few additional fields would greatly improve the
> usability of Turba/Horde for people using Outlook, Thunderbird and
> many other apps as well.
> Especially for those, where Horde is installed at an ISP (and the
> end user does not have influence on the fields).
>
> Ideally, the user could configure in the settings, which field
> should be displayed and which ones are not used a lot and therefore
> be hidden.
This can be configured for the address book list already, but not for
the full view. I could see how this *might* be useful if you have a
very large set of unused fields...but then, if they are unused, then
they really don't need to be in the config in the first place. Fields
can be grouped into tabs by the admin if having lots of fields on a
single "page" is the concern here.
>
> I don't know how much work it will be to implement that.
> But based on the few postings I read (especially on the
> Turba/Outlook2003 page, which unfortunately is not accessible
> anymore), it might be a matter of a few entries in a few files.
Well, like I said, adding the additional fields is very simple - which
is one reason we don't try to include everything for everybody. The
other reason is it's impossible to include everything for everybody ;)
Thanks,
mike
--
The Horde Project (www.horde.org)
mrubinsk at horde.org
"Time just hates me. That's why it made me an adult." - Josh Joplin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: PGP Digital Signature
URL: <http://lists.horde.org/archives/turba/attachments/20091208/843f6e99/attachment.bin>
More information about the turba
mailing list