On Tue, 15 Sep 2009 00:11:54 +0200 "Michael 'Mickey' Lauer" <mic...@vanille-media.de> said:
> On Monday 14 September 2009 04:07:43 Carsten Haitzler wrote: > > On Sun, 13 Sep 2009 21:42:49 -0400 Stefan Monnier > > <monn...@iro.umontreal.ca> > > > > said: > > > > Or more precisely, for "$DISPLAY on fso-controlled device" at > > > > runtime, not installation time. I think that mess will be larger than > > > > that of having two icons, menu items or whatever the launcher makes of > > > > it, for the user to choose between. > > > > > > The solution is to use a scheme where the blanking code and the > > > application use a standard protocol to sync-up. > > > > > > AFAIK, there is such a protocol already (which is hopefully used by all > > > tools like VLC, Xine, mplayer, totem, at least when in fullscreen > > > mode). So mokomaze should use it. And the FSO side should also > > > support it. > > > > x screensaver extension. you can request x to suspend blanking until u > > un-suspend it (or your x connection closes - eg u exit or crash). FSO tho > > wants to re-invent this wheel. > > Bzzt. Wrong. IdleNotifier is optional as are the rules in oeventsd. thats where i disagree. you have e-invented fso handling idle detection, even if optional. it should b the other way. fso is notified of idleness by the respective management systems. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community