On Mon, Jul 28, 2008 at 11:33 PM, John Stowers <[EMAIL PROTECTED]> wrote: > If another app calls into conduit using dbus, it will automatically > start, without the gui. If the user then starts Conduit from the > accessories menu, the Gui will be launched atop the already running > service. > > Basically I would prefer Conduit did not automatically start with the > session as it increases login time. > > There was originally a technical justification for having Conduit > running all the time, but since then we have got better about scanning > for appropriate connected hardware, instead of relying on Conduit > running all the time to notice when it gets plugged in. > > In future there may be additional reasons to have conduit running all > the time, such as 'always up to date' sync (only our gconf sync uses > this ATM, IIRC). > > In summary however, If I was a distributor, I would not autostart > conduit at login (yet).
I'm +1 on including conduit for as long as it: 1) does not autostart 2) gets its menu entry moved to System/Preferences for now It's quite useful when used as a daemon but pretty hard to grasp as soon as you get to the GUI. -- Patryk Zawadzki _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
