Jussi Kukkonen wrote: >Chen, Congwu wrote: >> Jussi Kukkonen wrote: >Changes like this are going to affect UI strings so if we want to do >this, let's do it ASAP. Sure, I will push the patch today.
>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" ACK. >* 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... This is not implemented so far. I may add it though but probably not today... >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? It sure does not make sense. The problem is what score is the limit? I think 1 is the right point, because score ==1 means the fingerprint actually doesn't match entirely while score>1 means the fingerprint matched somehow. Note that SyncEvolutionClient has a score of 2 at this moment because it has a special fingerprint entry 'default', it was meant to give SyncEvolutionClient a higher priority over other completely unmatched templates, but this means the limit of the score is not possible to define. I think I will remove the 'default' entry. Best Regards, Congwu _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
