karimsacre / google-shared-contacts-client

Automatically exported from code.google.com/p/google-shared-contacts-client
Apache License 2.0
0 stars 0 forks source link

Order of fields created = order of display in UI. Fax appears before phone and is non intuitive to end users. #12

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Cause the library to create a new contact with business phone and 
business fax details.
2. View the contact in the UI (contacts manager)
3. Notice that the Work Fax appears before the Work details (when viewed 
from top to bottom) 

What is the expected output? What do you see instead?
I would have expected that it was better to display the Work (business 
phone) before the fax. Using this with an organisation we have had many 
end users provide feedback that this is not intuitive for them and they are 
called a person's fax number by mistake.

What version of the product are you using? On what operating system?
1.1 on OS X

Please provide any additional information below.
The code frag is 
 self.primary_phone_numbers = ( # Field name, relation, priority
        ('Business Fax', gdata.data.WORK_FAX_REL, 0),
        ('Business Phone', gdata.data.WORK_REL, 0),
        ('Business Phone 2', gdata.data.WORK_REL, 1),
        ('Home Fax', gdata.data.HOME_FAX_REL, 0),
        ('Home Phone', gdata.data.HOME_REL, 0),
        ('Home Phone 2', gdata.data.HOME_REL, 1),
        ('Other Phone', gdata.data.OTHER_REL, 0 ),
        ('Mobile Phone', gdata.data.MOBILE_REL, 0),
        ('Pager', gdata.data.PAGER_REL, 0),

As you can see, the fields are added alphabetical order. I have cleared 
shared contacts and re-ordered the code and when re-run all is OK. The 
same cannot be easily done for users (profiles). I'd have to write a script to 
delete the fields and then re-add them in the required order. FYI, GADS 
also suffers from this "add fields in alpha order" issue.

Original issue reported on code.google.com by peter.he...@gmail.com on 4 Feb 2010 at 2:47

Attachments: