Hi, if the rev306 patch doesn`t fit into the concept i'm sorry, i got it wrong. my thought was to have all vcard 2.1 fields in the contact table. i'm no longer sure about that but i thought that only these fields which i created in the contact database table are allowed in the vcard 2.1 standard. So there is no need to have more then these fields in the database or otherwise you break the vcard 2.1 standard. There is also a newer vcard 3.0 standard but this standard isn't very common and there are only a few fields which are new. > 2006/8/10, Eric Stadtherr <[EMAIL PROTECTED]>: >> Should rev306 be backed out then? It goes against this concept. no problem about that - my patch was only a idea to improve the addressbook, if there are other ideas or concepts it will be great.
to make the addressbook look better even with all vcard fields in the database, it can be a option to show only these fields which are filled. And then if you edit the contact there can be a new button somewhere to view all fields. If you then fill a field which wasn't shown before (because it wasn't filled), it is shown after you saved your changes for the processed contact. -- have a nice weekend and best regards Tobias 'tri' Richter Visit me at: http://tobias.datenwerkstatt-richter.de/
