Subject: "Poke command and Inhibit commands removed from gnome-screensaver"

https://bugzilla.gnome.org/show_bug.cgi?id=579430
http://bugzilla.mplayerhq.hu/show_bug.cgi?id=1887

IRC conversation:

#gnome-hackers @ GIMPNet
----
<nirbheek> mccann, hey, about the gnome-screensaver poke command: iirc it was added because not every app out there can conform to GNOME's way of inhibiting the screensaver, and since gnome-screensaver stopped using the old xscreensaver way of preventing screensaver lock, the poke command was added
<mccann> I'm aware of that
<nirbheek> So, why remove it now?
<mccann> but if those apps are capable of using --poke they are capable of inhibiting
<mccann> removing it because it hasn't worked for a year or so
<nirbheek> That's because gnome-screensaver skipped 2.32
<nirbheek> mccann, afaik that the mplayer developers are averse to adding any dependency on dbus
<mccann> ha
<nirbheek> And gnome-screensaver-command --inhibit works just fine, so what's wrong with --poke?
<mccann> --inhibit is gone too
<mccann> it is all done by the session now
<mccann> the --inhibit was deprecated for a year or so as well
<nirbheek> mccann, this change breaks a lot of apps out there, I don't think this will do anything to improve the experience for GNOME users
<mccann> a lot?
<mccann> such as?
<nirbheek> Mplayer, all the KDE apps, for instance, because users can no longer use a command to inhibit the screensaver
<nirbheek> And since the screensaver panel doesn't have a way to disable the screensaver either, folks are stuck
<mccann> you can use a better movie player
<mccann> that's not exactly stuck
<nirbheek> for some things, mplayer is simply better than totem :)
* nacho (~nacho@far66.internetdsl.tpnet.pl) has joined #gnome-hackers
<mccann> just not this thing I guess - take your pick :)
<nirbheek> which is why I'm saying that users are stuck, you're giving them no way out
<mccann> um
<mccann> no, your app developers that refuse to use dbus are giving you no reason to keep using their app
<mccann> I'm sorry I don't know what to tell you
<nirbheek> mccann, let's look at this another way: what's the harm in keeping those commands around?
<mccann> besides use Totem
<mccann> nirbheek: dude, the command hasn't worked for a year
<nirbheek> mccann, in release versions it has worked just fine, and inhibit worked in the last release of g-screensaver
<mccann> Inhibit is done in gnome-session 
<mccann> we kept a transition proxy in place for a year
<nirbheek> `gnome-screensaver-command --inhibit` ← I mean this command
<nirbheek> aah, so what's the current way of inhibiting the screensaver via a command?
<mccann> that command used dbus
<nirbheek> Yes, and it worked, but it was removed
<mccann> <mccann> Inhibit is done in gnome-session 
<mccann> <mccann> we kept a transition proxy in place for a year
<mccann> now it is gone
<nirbheek> Which is why I asked, what was the harm in keeping it around?
<mccann> keeping what around?
<nirbheek> the inhibit command
<mccann> write one yourself
<mccann> have one shipped in mplayer so they don't have to use dbus
* DBO_ has quit (Ping timeout: 600 seconds)
<nirbheek> mccann, btw, the xscreensaver stuff in configure isn't used anymore, should probably be removed?
<mccann> yeah probably
<mccann> done
* jamesh has quit (Client exiting)
<nirbheek> mccann, also, the poke command is still around in the latest git, although it doesn't do anything, is that on purpose?
<mccann> because I'm not done
<nirbheek> okay
* vish has quit (Hmm? I just quit IRC, nothing to read here, move on…)
* vish (~vish@122.174.88.55) has joined #gnome-hackers
* amigadave (~amigadave@91-66-18-182-dynip.superkabel.de) has joined #gnome-hackers
<mccann> nirbheek: ok hopefully done for now
<mccann> would appreciate testing if you can
<mccann> its 3am and I've been working since 10am 
* nirbheek rebuilds gnome-screensaver from git
<nirbheek> mccann, thanks!