On Fri, 2007-02-23 at 10:12 +0100, Stephan Kulow wrote:
Am Donnerstag, 1. Juni 2006 20:06 schrieb Richard Hughes:
On Wed, 2006-05-31 at 17:48 -0700, Bastian, Waldo wrote:
I think this fits in really nice with the long-term vision that
Portland
has with DAPI (Deskop API). I would like
On Fri, 2006-06-02 at 15:30 +0200, Rodrigo Moya wrote:
I think it makes sense here, in power management interface, since
shutdown = power off. I would even add Reboot here, now that you
mention this.
Should we be using reboot or restart as an action? This is something
else that we should try
On Wed, May 31, 2006 at 11:01:31PM +0100, Richard Hughes wrote:
gnome power manager : org.gnome.PowerManager
gnome screensaver : org.gnome.ScreenSaver
ok, here are some random thoughts from the kdm guy.
we are talking about several things:
1) screen saver
2) dmps (display
On Wed, 2006-05-31 at 23:01 +0100, Richard Hughes wrote:
Name: Suspend
Args: (none)
Returns:BOOLEAN
Description:This call will attempt to suspend the system.
Name: Hibernate
Args: (none)
On Fri 02. Jun - 12:00:37, Kevin Ottens wrote:
Le jeudi 1 juin 2006 20:31, Richard Hughes a écrit :
On Thu, 2006-06-01 at 20:10 +0200, Kevin Ottens wrote:
To interact with the session we need this to be session context rather
than system context.
Not sure I understood you. AFAIK, you can
On Fri 02. Jun - 11:48:03, Richard Hughes wrote:
Okay, my first post to this list, so I hope I'm aiming in the right
direction.
gnome power manager : org.gnome.PowerManager
gnome screensaver : org.gnome.ScreenSaver
This should probably be cross desktop and less gnome-y
On Fri, 2006-06-02 at 15:30 +0200, Rodrigo Moya wrote:
for the same reason I think we should add the Reboot and keep Shutdown
methods, I think it's better if apps use only a standard interface for
all power management-related tasks than having to use dbus for some
operations, X libs for
On Fri, 2006-06-02 at 11:02 +0200, Alexander Larsson wrote:
Some systems also have a mode where they both save to disk and memory
at the same time, then they suspend, but if power goes low they power
down (and un-hibernate on startup).
You may be referring to Windows Vista, that's the only
On Friday 02 June 2006 15:30, Rodrigo Moya wrote:
[...]
Name: setDpmsMode
Args: STRING
value: on 100%
standby 80%
suspend 30W
off
On Fri, 2006-06-02 at 14:09 +0200, Holger Macht wrote:
Why do we need this in a power managmenet context. I think all desktop
will provide such a Shutdown method via dbus regardless of power
management.
Shutdown on the session is save+close documents, log, warn user etc then
shutdown, rather
On Fri, 2006-06-02 at 12:42 +0200, Kevin Ottens wrote:
Le vendredi 2 juin 2006 12:14, Holger Macht a écrit :
On Fri 02. Jun - 12:00:37, Kevin Ottens wrote:
I'll give more thought to this and maybe rework my plans. That's an
interesting point of view difference. =)
Hence why, I won't
On Fri, 2006-06-02 at 11:02 +0200, Alexander Larsson wrote:
Some systems also have a mode where they both save to disk and memory
at the same time, then they suspend, but if power goes low they power
down (and un-hibernate on startup).
Wouldn't it make sense to support a mode like that too?
Richard Hughes wrote:
On Fri, 2006-06-02 at 14:09 +0200, Holger Macht wrote:
[snip]
How is this ment to be? Does it just a mirror the corresponding HAL
methods power_management.can_hibernate/suspend? If so, I think we don't
need it. Desktops will have a close connection to Hal anyway to query
Danny Kukawka wrote:
On Friday 02 June 2006 15:30, Rodrigo Moya wrote:
[...]
Name: setDpmsMode
Args: STRING
value: on 100%
standby 80%
suspend
On Fri 02. Jun - 16:39:37, Richard Hughes wrote:
On Fri, 2006-06-02 at 11:02 +0200, Alexander Larsson wrote:
Some systems also have a mode where they both save to disk and memory
at the same time, then they suspend, but if power goes low they power
down (and un-hibernate on startup).
On Wed, 2006-05-31 at 23:01 +0100, Richard Hughes wrote:
The GNOME Screensaver DBUS API
--
...
Name: setActive
Args: DBUS_TYPE_BOOLEAN state
state: TRUE to request activation,
On wo, 2006-05-31 at 23:01 +0100, Richard Hughes wrote:
The interfaces we have now are attached.
/me still thinking about a standard dbus interface definition format...
Comments appreciated.
Richard
___
xdg mailing list
xdg@lists.freedesktop.org
Hi David,
David Zeuthen wrote:
[snip]
I think I only have one comment on the current spec:
Name: Inhibit
Args: DBUS_TYPE_STRING application-name
DBUS_TYPE_STRING reason for inhibit
Returns:INT cookie
Hi Rodrigo,
Rodrigo Moya wrote:
On Wed, 2006-05-31 at 17:48 -0700, Bastian, Waldo wrote:
The screensaver interface looks good. What is the use case for the
Poke method?
I guess it can be used by apps like video players to prevent the
screensaver to fire while showing the movie.
It is
Hi David,
David Zeuthen wrote:
On Thu, 2006-06-01 at 10:07 -0400, William Jon McCann wrote:
Hi Waldo,
Bastian, Waldo wrote:
The screensaver interface looks good. What is the use case for the
Poke method?
The Poke method is a way to simulate user input. It is the programmatic
On Thu, 2006-06-01 at 10:07 -0400, William Jon McCann wrote:
Hi Waldo,
Bastian, Waldo wrote:
The screensaver interface looks good. What is the use case for the
Poke method?
The Poke method is a way to simulate user input. It is the programmatic
equivalent to moving the mouse back
Hi Waldo,
Bastian, Waldo wrote:
The screensaver interface looks good. What is the use case for the
Poke method?
The Poke method is a way to simulate user input. It is the programmatic
equivalent to moving the mouse back and forth or hitting the Shift key
or something. If the screensaver
On Wed, 2006-05-31 at 17:48 -0700, Bastian, Waldo wrote:
I think this fits in really nice with the long-term vision that
Portland
has with DAPI (Deskop API). I would like to suggest to rename the
interface org.gnome.* to org.freedesktop.* and host them as part of
DAPI in the Portland CVS (See
Hi Kevin!
On Thu, 2006-06-01 at 20:10 +0200, Kevin Ottens wrote:
Le jeudi 1 juin 2006 00:01, Richard Hughes a écrit :
Okay, my first post to this list, so I hope I'm aiming in the right
direction.
gnome power manager : org.gnome.PowerManager
gnome screensaver :
On Thu, 2006-06-01 at 11:03 -0700, Bastian, Waldo wrote:
Does the current dbuslib implementation allow you to specify what to do
when the dbus connection gets dropped? If not, then I think that should
be added.
Yes. Use dbus_connection_set_exit_on_disconnect (DBusConnection*).
David
On Thu 01. Jun - 19:31:36, Richard Hughes wrote:
On Thu, 2006-06-01 at 20:10 +0200, Kevin Ottens wrote:
Le jeudi 1 juin 2006 00:01, Richard Hughes a écrit :
Okay, my first post to this list, so I hope I'm aiming in the right
direction.
gnome power manager :
On Thu, 2006-06-01 at 20:44 +0200, Holger Macht wrote:
To interact with the session we need this to be session context rather
than system context. Plus with David's work, the distinction between
session and system will be a lot smaller. For powersaved, any session
program can just process
On Thu, 2006-06-01 at 15:05 -0400, David Zeuthen wrote:
On Thu, 2006-06-01 at 20:44 +0200, Holger Macht wrote:
To interact with the session we need this to be session context rather
than system context. Plus with David's work, the distinction between
session and system will be a lot
On Thu, 2006-06-01 at 21:21 +0200, Holger Macht wrote:
The problem, Holger, is that if the org.freedesktop.PowerManager service
is on the system bus, it's awkward and backwards to interact with the
desktop session using notifications and dialogs. It's not impossible,
just pretty awkward.
The screensaver interface looks good. What is the use case for the
Poke method?
Power manager stuff looks nice as well, but maybe the KDE HW ppl can
comment on that a little bit better.
I think this fits in really nice with the long-term vision that Portland
has with DAPI (Deskop API). I would
30 matches
Mail list logo
