Post by Simon CPost by Simon CExtend the idea of categories in the existing
ringtone/wallpaper tabs
Post by Simon Cto allow assignment to specific numbers as well as category.
Ideally, since the ringtone and wallpaper assignments go with
the numbers, they should be grouped with the numbers. We
might be looking for a lesser evil in this case. Let me
ponder on this some more.
The database schema is part of this as well.
Ideally a user who imports a phonebook from an LG phone with one ringtone
for numbers in a contact could export this to a moto and have the ringer
preserved on all entries in the same contact, the users should just be able
to set a single ringer for a moto and have it apply to all numbers for a
contact, they should not *have* to select a ringtone on a per number basis,
they should just *have the option* to do so.
It is possible today (from a database perspective) to add multiple ringtones
for a given contact with the the same category, although if you try to send
to the phone only the first will get used.
If you extend the existing schema to include an optional number/email or
index to same you will have something that is compatible with existing code.
The existing code would ignore the new field in the database.
So for the moto instead of
res['ringtones'].append({'ringtone': tone, 'use': 'call'})
You would have
res['ringtones'].append({'ringtone': tone, 'use': 'call',
'number':'123456'})
Or
res['ringtones'].append({'ringtone': tone, 'use': 'message',
'number':'123456'})
res['ringtones'].append({'ringtone': tone, 'use': 'e-mail',
'address':'***@bitpim.org'})
On the contact gui editor you would add a new new combo box to the ringtone
to select the specific number/email that the number applied to, the list
would be populated based on the category selected. By default you would
select "All" as the numbers to apply the ringtone to.
Simon