On Fri, 11 Aug 2006, ext Havoc Pennington wrote:
A good API for saving window state is probably something like:
gtk_window_save_state(GtkWindow *window, const char *window_key);
which would magically know which things to save (including
_NET_WM_STATE), would magically save a different
On Mon, 2006-08-14 at 11:18 -0500, Federico Mena Quintero wrote:
On Sat, 2006-08-12 at 12:00 +0100, Ross Burton wrote:
libgconf-bridge doesn't handle per-machine state yet, but it will handle
multiple windows just fine: you give it a gconf path prefix to persist
the states at, so for
On Mon, 2006-08-14 at 12:37 -0400, Germán Poó Caamaño wrote:
On Mon, 2006-08-14 at 11:18 -0500, Federico Mena Quintero wrote:
On Sat, 2006-08-12 at 12:00 +0100, Ross Burton wrote:
libgconf-bridge doesn't handle per-machine state yet, but it will handle
multiple windows just fine: you
On Mon, 2006-08-14 at 12:30 -0500, Shaun McCance wrote:
On Mon, 2006-08-14 at 12:37 -0400, Germán Poó Caamaño wrote:
On Mon, 2006-08-14 at 11:18 -0500, Federico Mena Quintero wrote:
On Sat, 2006-08-12 at 12:00 +0100, Ross Burton wrote:
libgconf-bridge doesn't handle per-machine
On Mon, 2006-08-14 at 16:18 -0400, Germán Poó Caamaño wrote:
Because the key is not used anymore, or there was a typo in the previous
version, or the application got merged into another one, the keys were
sorted out different for any reason, etc.
I still have net-rhythmbox while I have
On Fri, 2006-08-11 at 16:04 -0500, Federico Mena Quintero wrote:
The very act of wanting to preserve the user's window geometries means
that you are storing user preferences. Let's not make a semantics
argument out of this. GConf *is* the GNOME way of storing
configuration-like information,
Havoc Pennington wrote:
A good API for saving window state is probably something like:
gtk_window_save_state(GtkWindow *window, const char *window_key);
which would magically know which things to save (including
_NET_WM_STATE), would magically save a different state per screen size,
On Fri, 2006-08-11 at 16:04 -0500, Federico Mena Quintero wrote:
On Fri, 2006-08-11 at 11:22 +0100, Bastien Nocera wrote:
I've written up on GNOME Goal #3:
http://live.gnome.org/GnomeGoalsSaveState
Currently, a lot of applications will be using GConf to save state, like
window sizes,
Marc-André Lureau wrote:
I might be the only one, but I would rather let Metacity (or any
window manager) do the job of positionning/sizing my windows. As you
could read on the msdn blog, saving state of an application is really
tricky.
The window manager does not have enough
On Fri, 2006-08-11 at 11:22 +0100, Bastien Nocera wrote:
Heya,
I've written up on GNOME Goal #3:
http://live.gnome.org/GnomeGoalsSaveState
Currently, a lot of applications will be using GConf to save state, like
window sizes, whether or not a window is maximised on startup, etc.
This
Heya,
I've written up on GNOME Goal #3:
http://live.gnome.org/GnomeGoalsSaveState
Currently, a lot of applications will be using GConf to save state, like
window sizes, whether or not a window is maximised on startup, etc.
This is against GConf policy, as GConf might be read-only, or
On Fri, 2006-08-11 at 11:22 +0100, Bastien Nocera wrote:
Heya,
I've written up on GNOME Goal #3:
http://live.gnome.org/GnomeGoalsSaveState
Currently, a lot of applications will be using GConf to save state, like
window sizes, whether or not a window is maximised on startup, etc.
This
gnome_config is deprecated, in favor of GKeyFile.
Unfortunately, GKeyFile is a lower-level API than gnome_config, making
you do things like figure out where to put the file yourself (and
really, with key:value files, figuring out where to put it is the
harder part).
-David
On 8/11/06, Shaun
On Fri, 2006-08-11 at 11:03 -0700, David Trowbridge wrote:
gnome_config is deprecated, in favor of GKeyFile.
Unfortunately, GKeyFile is a lower-level API than gnome_config, making
you do things like figure out where to put the file yourself (and
really, with key:value files, figuring out
A good API for saving window state is probably something like:
gtk_window_save_state(GtkWindow *window, const char *window_key);
which would magically know which things to save (including
_NET_WM_STATE), would magically save a different state per screen size, etc.
There's no way apps will
On Fri, 2006-08-11 at 11:22 +0100, Bastien Nocera wrote:
I've written up on GNOME Goal #3:
http://live.gnome.org/GnomeGoalsSaveState
Currently, a lot of applications will be using GConf to save state, like
window sizes, whether or not a window is maximised on startup, etc.
This is
16 matches
Mail list logo
