[turba] What is the status of Turba (contact fields) ?

[lst_hoe02 at kwsoft.de]

Zitat von Rolf Gloor <thunderbird at glr.ch>:

> Am 03.12.2009 19:31, schrieb Michael J. Rubinsky:
>>
>> Turba can support pretty much any field that you configure it to
>> understand...but this *has* to be done by the administrator. If your
>> provider only allows the limited number of contact fields, then that is
>> all you get. In other words, Turba does have "better support for many
>> more fields", but you must get the server administrator to configure them.
>>
>>
>
> Hi Michael
>
> Thanks for your feedback.
>
> A) Suggestion
> My suggestion is  - if technically possible -  to include at least  
> the set of ALL possible Outlook fields.
> For an ISP, running many, many servers with Horde,  it will be a  
> nightmare to go out an change one setting. And having to modify all  
> installations might be too much work and risk. They usually prefere  
> not to touch the default / standard setup for reasons of easier,  
> less risky upgrading.
>
> => 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.


>
> B) Question
> Is there somewhere a list, showing fields are supported in the  
> default setup? (Standard "out-of-the-box".)
>
> Preferable for
> - Turba 2.3.1 (which still runs at my ISP. Just for comparison reason.)
> - Turba 2.3.2
> - and also the upcoming Turba 2.3.3

There is no change in 2.3.x and you can extract it out of the SQL scripts:

     object_firstname VARCHAR(255),
     object_lastname VARCHAR(255),
     object_middlenames VARCHAR(255),
     object_nameprefix VARCHAR(32),
     object_namesuffix VARCHAR(32),
     object_alias VARCHAR(32),
     object_photo TEXT,
     object_phototype VARCHAR(10),
     object_bday VARCHAR(10),
     object_homestreet VARCHAR(255),
     object_homepob VARCHAR(10),
     object_homecity VARCHAR(255),
     object_homeprovince VARCHAR(255),
     object_homepostalcode VARCHAR(10),
     object_homecountry VARCHAR(255),
     object_workstreet VARCHAR(255),
     object_workpob VARCHAR(10),
     object_workcity VARCHAR(255),
     object_workprovince VARCHAR(255),
     object_workpostalcode VARCHAR(10),
     object_workcountry VARCHAR(255),
     object_tz VARCHAR(32),
     object_geo VARCHAR(255),
     object_email VARCHAR(255),
     object_homephone VARCHAR(25),
     object_workphone VARCHAR(25),
     object_cellphone VARCHAR(25),
     object_fax VARCHAR(25),
     object_pager VARCHAR(25),
     object_title VARCHAR(255),
     object_role VARCHAR(255),
     object_logo TEXT,
     object_logotype VARCHAR(10),
     object_company VARCHAR(255),
     object_category VARCHAR(80),
     object_notes TEXT,
     object_url VARCHAR(255),
     object_freebusyurl VARCHAR(255),
     object_pgppublickey TEXT,
     object_smimepublickey TEXT,

As said otherwise there are improvements in mapping these per SyncML  
but only as far as needed by others.

>
> C) another Question
> On the horde web site, I could not find any roadmap regarding  
> further releases:
> - When will the next minor framwork release happen. Horde 3.3.6,  
> Turba 2.3.3, etc.
> - When will the new major framework release happen, the next  
> generation Horde 4.x (which is in work now, right? In the git?)

http://www.horde.org/horde/roadmap/
http://www.horde.org/turba/roadmap/

But this are only whishlists :-)
You can always speed it up by get some PHP programer working on it...

Regards

Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6397 bytes
Desc: S/MIME krytographische Unterschrift
URL: <http://lists.horde.org/archives/turba/attachments/20091208/095ebfb2/attachment.bin>