[Syncevolution-issues] [Bug 7089] pairing with Bluetooth devices
http://bugzilla.moblin.org/show_bug.cgi?id=7089
--- Comment #4 from pohly <patrick.ohly(a)intel.com> 2009-11-24 06:00:32 PST ---
(In reply to comment #3)
The current approach is a little from column a, a little from column
b.
If the device is detected as supporting syncml with moblin by the bluetooth
panel during pairing then:
1) a config file is silently created for the device. this needs to be managed
so that it is removed if the pairing is revoked by the bluetooth panel.
We would implement this slightly differently internally for new devices:
instead of creating a real configuration on disk, we would create a template in
memory.
The template can stay in memory as long as long as the D-Bus server runs. We
don't have to implement anything to remove it. If the user decides against
configuring it, the D-Bus server will quit eventually and thus drop the
template. If the user accepts, the template will be available.
2) an option is displayed to the user in the post pairing workflow
telling them
that they can now sync with this device (options are presented for all
supported profiles for each device).
What kind of different profiles do you mean? Is someone already working on
this?
If the user selects this they are taken to
the 'change sync service' or 'setup sync service' area of the sync
app/settings
depending on whether they have already setup a sync service.
So we need a new command line option in the sync-UI:
--select "config name" - switch to existing config or
create it anew from a template
3) the silently created config file is displayed as a setup option
within the
service setup workflow. Device's are shown in a different list to 'pure'
network syncs but otherwise treated the same.
Jussi, I assume that you know how to do this.
--
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.