Chen, Congwu wrote:
Jussi Kukkonen wrote:
> I'm currently using the first part of device template fingerprint as the
> name. That is currently not very user friendly but I'm not sure what
> would be the right way fix that: Is there a reason why the "first
> fingerprint" couldn't be 'Nokia 7210' instead of
We had discussions about this, sorry for forgetting to implement this. I will
do this. So you can get both 'device name' and 'template name' from the
So I'd have a device name when it's known, otherwise I'd use the
template name... that would probably work, althpough it does have the
same problem I mentioned: People might not know what the categories
(such as "Nokia S40") mean. I think your suggestion is still better.
Maybe something like this would work "We're not sure of the exact model,
but this looks like a "Nokia S40" device. ...".
Changes like this are going to affect UI strings so if we want to do
this, let's do it ASAP.
Now that I've implemented some ui elements on top of this data already,
I have some additional wishes:
* the names should only include manufacturer/device/platform names to
avoid translation problems, so my example of "Nokia S40 phone" should
actually be "Nokia S40"
* the device type would be nice to have as a separate property (it is
not critical though). We discussed this at some point but I don't
remember whether it was implemented...
Additional question: When there are templates with a score above a limit
X, should I hide the lower score templates? As in, if the bluetooth
device name has "Nokia" in it, does it make sense to show the
"syncevolution client" template?