On Thu, 2007-12-27 at 12:25 +0000, John Carr wrote: > On Dec 27, 2007 10:08 AM, Mark Ellis <[EMAIL PROTECTED]> wrote: > > > I prefer this kind of thing not to be implemented in kitchensync, > > > though that is probably where the opensync people would put it. Doing > > > that means that multisync, gnome-sync and any other opensync client > > > would have to reimplement it. > > > > > > John > > > > Sounds like it should be started by trayicon or something similar. Isn't > > there a dbus interface ? Couldn't we configure dbus to fire it up when > > something attaches to the service ? John said he was adding a fix for > > when odccm and/or a device was not present, should it just go in the > > session startup ? > > > > Mark > > Wearing my cross device, cross distro, working together hat: Really > reluctant to back anything trayicon related. IMO, in the same way that > there is opensync there should be one tray icon system manager 'thing' > that we plug into. Right now gnome-phone-manager is probably the > closest to that... >
I'm not plugging trayicon per se, just something that is running on login as the user that can see a device plugged in and kick off sync-engine. > I like the idea of dbus activation, and using HAL to automatically > close sync-engine when the device is unplugged, but am not how the > device will cope if it is plugged in and the HTTP server for AirSync > is not responding straight away. Don't know enough (anything) about airsync to say. Sync-engine could listen to hal events to shut itself down, or just shut down a connection to that device, but the startup part is a little foggier. Mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
