wikipbx-dev team mailing list archive

[Stas Shtin <antisvin@xxxxxxxxx>]

>> 3. Is there any use case when you would need to export only part of your
>> contacts? Maybe we need an ability to filter contacts by organisation
>> and search by phone number/name/title. Also, adding checkboxes that can
>> be deselected to exclude contacts from being exported seems like a good
>> idea to me.
>
> I don't but maybe others have :)
I've added this now.

>
>> 4. numbers = models.CharField(_(u"caller ID number"), max_length=25)
>>
>> So is it one number or multiple? Maybe we should have fields for work
>> and home numbers.
>
> I've started with multiple in one field but then moved to one, agree
> need to split at least to home, work and mobile. Even fax maybe?
Yeah, I guess we need all of that. Also, vCard name and full name fields
should look like:

N:Gump;Forrest
FN:Forrest Gump


N     Name     A structured representation of the name of the person,
place or thing associated with the vCard object.
FN     Formatted Name     The formatted name string associated with the
vCard object


So name field should be split as well.

>
>> 5. When in template you have:
>>          {% trans "Caller ID number" %}
>>
>> and in model:
>> _(u"caller ID number")
>>
>> that creates two localization strings. In order to create only one
>> string with correct capitalization in templates, you should write it
>> like:
>>
>> {{ _("caller ID number")|capfirst }}
>>
>> It looks somewhat uglier than it should, but I haven't found any better
>> solution that works for all cases.
>
> Sure this is an oversight
Actually, I've meant all table headers that are based on model fields
:-) , so in contacts list template it includes notes, name, etc. I've
fixed that myself, just remember it for the future.

>> 6. Instead of "Siemens Gigaset" format it should be called vCard 2.1. We
>> certainly need to add 3.0 before releasing this, but it's probably a
>> matter of using a slightly different template. Export page should also
>> contain a brief note about which format is used by which phone
>> manufacturers, to make it less confusing for the new users.
>
> Ok, but i only have gigaset phones at hand :)
That shouldn't be a problem, since vCard is a common standard. I think
only 3.0 was formally standartized, but it has just slight syntactic
differences from 2.1. I've tried importing exported vCards to evolution
and it worked fine in both formats.

>
>> 8. Export templates should be stored in django templates (i.e.
>> contacts/templates/vcard_2_1.vcf). Unset entries should be skipped when
>> generating exported data to keep file size down.
>
> What do you mean by unset entries?
Empty values.

>
>> 9. If you want to export JSON data only to freeswitch, the decorator
>> should be checking for IP address set in event socket rather than only
>> localhost. This way you can be using it with freeswitch running on a
>> different server.
>
> Yeah, that was the plan; will use that. Does the localhost_only
> decorator would be of any use for other stuff?
>
Probably not.