http://bugzilla.moblin.org/show_bug.cgi?id=9155
--- Comment #3 from Chen Congwu <congwu.chen(a)intel.com> 2010-01-21 00:15:22 PST
---
(In reply to comment #2)
(In reply to comment #1)
> The problem is allow fuzzy based template picking for device sync (and now also
> for http clients).
Why does the template selection use a fuzzy search at all?
SyncConfig::createPeerTemplate() takes the name of a template, not a
<Manufacturer>_<Model> string.
I'm not convinced that it should do a fuzzy match. When a user has a typo in
the --template parameter, then he shouldn't silently end up using the wrong
template.
I also don't see it mentioned in the commit message of your template search
patch. It mentioned --template ?, but not that --template <foo> also works
differently from before. If you knowingly change exiting user interfaces or the
D-Bus API, then *always* describe this clearly.
Can we revert to the old behavior?
I see, so that should be an exact match for
createPeerTemplate and fuzzy match
for matchPeerTemplate.
Also, looking at the code again, the directory walking in
SyncConfig::createPeerTemplate() seems to be very similar (identical?) to the
one in SyncConfig::matchPeerTemplates(). Can the common code be put into an
utility function?
I remembered I once intends to merge them and gave up. The code
then changed a
lot and reviewed it this time, they look exactly the same !? Have I missed
something?
--
Configure bugmail:
http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.