Ohly, Patrick wrote:
>On Tue, 2010-03-23 at 01:30 +0000, Chen, Congwu wrote:
>> Ohly, Patrick wrote:
>> >On Mon, 2010-03-22 at 10:20 +0000, Jussi Kukkonen wrote:
>> >> Chen, Congwu wrote:
>> >> > Jussi Kukkonen wrote:
>> Both 'deviceName' and 'fingerprint' was already supported by the DBus API,
>> you can get the value using the two properties. What we try to finalize is to
>> make sure the first entry of the fingerprint will be the template name.
>>
>> >... which we don't know at the moment.
>> We know the device name from Bluez, like ('Nokia N900', 'Nokia 7210c')
>
>I thought that device name != manufacturer+model?
>
>Isn't the device name something chosen by the user? There's no
>guaruantee that this includes either manufacturer or model.
Yes, we did not have any assumption about the device name. The example here
maybe misleading, but this is what we got in default case (i.e. user did not
change
the device name).
If user set an arbitrary name say naming his N900 as 'myPhone', what the UI
will show
Is:
"
myPhone
We don't know what the device is exactly..."
>> >For example, suppose we have "fingerPrint = Nokia 7120c, Nokia N85".
>> >I would find it confusing to have a "Nokia N85" and then being told by
>> >the GUI tells me that "we think you have a Nokia 7120c".
>> I think the GUI can still tell you "we think you have a Nokia N85, because it
>> is a perfect match and we know the device name is Nokia N85, though the
>> template name is Nokia 7210c.
>
>Does the GUI get enough information for this already? If yes, can you
>describe how Jussi can implement this? If no, what needs to be changed
>by whom?
Yes, I think so. The temporary template has 'deviceName' and 'fingerPrint'
property
for this two.
Best Regards,
Congwu
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
