http://bugzilla.moblin.org/show_bug.cgi?id=7089
--- Comment #3 from nedrichards <[email protected]> 2009-11-24 05:47:16 PST --- 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. 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). 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. 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. The latest bluetooth panel wireframes for netbook and mid show the bluetooth panel side of this. The latest sync wireframes for mid show most of this (they're still not concrete on what actually happens when the user selects the precreated profile) and the next set for netbook will show it as well. -- 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. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
