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:
> >> >> 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 'nokia_7210c'?
> >> > 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
> >> > DBus server.
> >>
> >> I tried to use this but I'm not sure what I'm supposed to do... I don't
> >> see any new properties. Are you embedding both pieces of data in the
> >> fingerPrint? How do I find out the exact device model if syncevolution
> >> knows it?
> 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.
> , what
> we don't know is the platform (S40, S60, Maemo..)
> This is the missing part, we can add a 'platform' property for each
> template:
> Since we don't know the platform automatically, we can't use this for
> matching;
> it will help when there is no exact match for a phone, the popped list of
> templates
> have an additional property, helping advanced user better select a working
> template
> manually.
We don't need something for advanced users :-/ We need something that
works for all users, as good as possible.
> >> Think of a situation where you've added several S40 phones as
> >> supported models.
> >
> >Advantage of "extend fingerPrint": less templates on disk, less data to
> >transfer via D-Bus, small list of configs to choose from in GUI
> >
> >Disadvantage of "extend fingerPrint": as soon we have more than one
> >model, the first entry can no longer be a simple "Manufacturer Model"
> >string.
> >
> >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?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
