Re: missing workflows with gnome-shell
On Sun, Feb 20, 2011 at 6:11 PM, Giovanni Campagna
scampa.giova...@gmail.com wrote:
Il giorno dom, 20/02/2011 alle 00.16 +0100, Alessandro Crismani ha
scritto:
Il giorno sab, 19/02/2011 alle 19.02 +0100, Giovanni Campagna ha
scritto:
Il giorno lun, 07/02/2011 alle 22.04 +0100, Alessandro Crismani ha
scritto:
Il giorno lun, 07/02/2011 alle 10.21 +0100, Thomas Bouffon ha
scritto:
[...]
I'm copy and pasting it here, it's not that long. It is a slightly
modified version of your extension (renamed variables and minor
edits, I
rewrote it for learning purposes, hope you don't mind), that does not
use Gconf (I planned to add class and titles and I wanted an easily
modifiable config, so I'm directly using an array in the extension).
Here it is, and it works with an up to today build (2.91.6):
[...]
That's the problem. I'm clueless about Gsettings and how to store
into|
use|abuse it. As usual, I should do a little bit of research, but I
have
yet to find an agreement with my to-do list :)
I've taken the liberty to include your code in gnome-shell-extensions
I browsed the repository and noted that I am listed as the original code
in the metadata.json. The code I've mailed is a slightly modified paste
of Thomas Bouffon's extension, so could you please credit him instead of
me? :)
I've added Thomas, but kept you as well, because you're work of adapting
the extension to avoid using the overview code was very important in
porting to 2.91.6.
after some modifications to make it work with GSettings.
Thanks very much for taking the effort to modify it and port it to
GSetting, I'll try it as soon as I can. The extensions repo is a great
idea, so is your work on it :)
If you want to play with it, it is the auto-move-windows extension. The
set of applications can be modified with:
gsettings set org.gnome.shell.extensions.auto-move-windows
application-list ['app-id.desktop:3']
(I'm using desktop files, obtained using ShellWindowTracker /
ShellAppSystem, which are more reliable than window classes).
You're example should roughly be
gsettings set org.gnome.shell.extensions.auto-move-windows
application-list
['rhythmbox.desktop:2','evolution.desktop:1','fedora-liferea.desktop:1']
Does your version work in the new workspace thumbnail Shell. My
version failed due to auto management of workspaces. Let's say that I
have only one workspace, and I want Rhythmbox on the third. I call the
add_workspace_by_index twice, but the second added workspace is deleted
because it is empty. Right now I am pinning the first four workspace,
so they don't get deleted, but it is a ugly hack.
Unfortunately, we cannot block the shell from collecting empty
workspaces, so if the number of workspaces is greater than then the
available, the application will end up on the last one.
In my case it still works because I have 6 (5+1) workspaces available,
which is enough for the applications I launch.
Hi !
Actually you can override the Main._checkWorkspaces function. I modified it
so that it only removes the last workspaces if there are more than one. Thus
if the first workspace is empty but the 2nd one is not, the 1st won't be
deleted.
I also modified _ensureAtLeastWorkspaces to move the window to the new
workspace created, so that new workspaces are not collected if there are
more than 2.
This workflow suits my needs, at least (I generally use 4 Desktops and put
Firefox on the 3rd, which now guarantees me the 4 desktops.)
I renamed extension.js to extension.txt and attached it here.
Any remarks are welcome !
Cheers,
Thomas
// Start apps on custom workspaces
const Glib = imports.gi.GLib;
const Gio = imports.gi.Gio;
const Lang = imports.lang;
const Mainloop = imports.mainloop;
const Shell = imports.gi.Shell;
const St = imports.gi.St;
const Main = imports.ui.main;
const SETTINGS_SCHEMA = 'org.gnome.shell.extensions.auto-move-windows';
const SETTINGS_KEY = 'application-list';
function WindowMover() {
this._init();
}
WindowMover.prototype = {
_init: function() {
this._settings = new Gio.Settings({ schema: SETTINGS_SCHEMA });
this._windowTracker = Shell.WindowTracker.get_default();
let display = global.screen.get_display();
// Connect after so the handler from ShellWindowTracker has already run
display.connect_after('window-created', Lang.bind(this,
this._findAndMove));
},
_ensureAtLeastWorkspaces: function(num,window) {
for (let j = global.screen.n_workspaces; j = num; j++) {
window.change_workspace_by_index(j-1, false,
global.get_current_time());
global.screen.append_new_workspace(false, 0);
}
},
_findAndMove: function(display, window, noRecurse) {
if (!this._windowTracker.is_window_interesting(window))
return;
let spaces =
Re: missing workflows with gnome-shell
Il giorno mer, 23/02/2011 alle 10.28 +0100, Thomas Bouffon ha scritto:
Actually you can override the Main._checkWorkspaces function. I
modified it so that it only removes the last workspaces if there are
more than one. Thus if the first workspace is empty but the 2nd one is
not, the 1st won't be deleted.
I also modified _ensureAtLeastWorkspaces to move the window to the new
workspace created, so that new workspaces are not collected if there
are more than 2.
This workflow suits my needs, at least (I generally use 4 Desktops and
put Firefox on the 3rd, which now guarantees me the 4 desktops.)
I renamed extension.js to extension.txt and attached it here.
Any remarks are welcome !
Cheers,
Thomas
Woah, awesome!
Didn't know that you can override the GS's main cycle, this is plain
wonderful :), I do not have to maintain my sick branch anymore. I tried
your modded extension but it fails inside ensureAtLeastWorkspace saying
that window.change_workspace_by_index() is not a function. I think that
window is not defined there (I might be wrong, I am in clear
difficulty with javascript variables management, used to old C++ where
you declare everything).
I've changed the extension to something that seems to work for me. I've
also changed the Main behaviour, marking as not empty all the workspaces
before the last one that contains a window, instead of breaking the
delete cycle. The extension is enclosed in the mail, any feedback is
welcomed :)
Cheers,
Alessandro
// Start apps on custom workspaces
const Glib = imports.gi.GLib;
const Gio = imports.gi.Gio;
const Lang = imports.lang;
const Mainloop = imports.mainloop;
const Shell = imports.gi.Shell;
const St = imports.gi.St;
const Main = imports.ui.main;
const SETTINGS_SCHEMA = 'org.gnome.shell.extensions.auto-move-windows';
const SETTINGS_KEY = 'application-list';
function WindowMover() {
this._init();
}
WindowMover.prototype = {
_init: function() {
this._settings = new Gio.Settings({ schema: SETTINGS_SCHEMA });
this._windowTracker = Shell.WindowTracker.get_default();
let display = global.screen.get_display();
// Connect after so the handler from ShellWindowTracker has already run
display.connect_after('window-created', Lang.bind(this,
this._findAndMove));
},
_ensureAtLeastWorkspaces: function(num, window) {
for (let j = global.screen.n_workspaces; j = num; j++) {
window.change_workspace_by_index(j - 1, false,
global.get_current_time());
global.screen.append_new_workspace(false, 0);
}
},
_findAndMove: function(display, window, noRecurse) {
if (!this._windowTracker.is_window_interesting(window))
return;
let spaces = this._settings.get_strv(SETTINGS_KEY);
let app = this._windowTracker.get_window_app(window);
if (!app) {
if (!noRecurse) {
// window is not tracked yet
Mainloop.idle_add(Lang.bind(this, function() {
this._findAndMove(display, window, true);
return false;
}));
} else
log ('Cannot find application for window');
return;
}
let app_id = app.get_id();
for ( let j = 0 ; j spaces.length; j++ ) {
let apps_to_space = spaces[j].split(:);
// Match application id
if (apps_to_space[0] == app_id) {
let workspace_num = parseInt(apps_to_space[1]) - 1;
this._ensureAtLeastWorkspaces(workspace_num, window);
window.change_workspace_by_index(workspace_num, false,
global.get_current_time());
}
}
}
}
function main(extensionMeta) {
Main._checkWorkspaces=function(){
let i;
let emptyWorkspaces = [];
for (i = 0; i Main._workspaces.length; i++)
emptyWorkspaces[i] = true;
let windows = global.get_window_actors();
for (i = 0; i windows.length; i++) {
let win = windows[i];
if (win.get_meta_window().is_on_all_workspaces())
continue;
let workspaceIndex = win.get_workspace();
for (j = 0; j = workspaceIndex; j++)
emptyWorkspaces[j] = false;
}
// If we don't have an empty workspace at the end, add one
if (!emptyWorkspaces[emptyWorkspaces.length -1]) {
global.screen.append_new_workspace(false,
global.get_current_time());
emptyWorkspaces.push(false);
}
// Delete other empty workspaces; do it from the end to avoid index
changes
for (i = emptyWorkspaces.length - 2; i = 0; i--) {
if (emptyWorkspaces[i])
global.screen.remove_workspace(Main._workspaces[i],
global.get_current_time());
}
Main._checkWorkspacesId = 0;
return false;
};
new WindowMover();
}
Re: missing workflows with gnome-shell
Il giorno mer, 23/02/2011 alle 13.23 +0100, Thomas Bouffon ha scritto: Hmm that's weird; window should be defined, it's an argument to the ensureAtLeastWorkspace function, and in findandmove, window is also part of the arguments and what actually triggers the findandmove event . Moreover, in the part that works for you, the whole code for the windowmover class is unmodified. Stupid me! I probably copied only a part of what you posted and the ensureAtLeastWorkspace prototype was left as in git, hence passing only num. I played around with the extension folder and messed up things to install the gsettings schema, I probably overwrote some of your changes and did not restore them, I added the window argument, without noticing that you did that before! I'm sorry, my bad. Besides, thanks a lot for the let j tip :) Cheers, Alessandro ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
Okay, so now we have the same version and it works for both of us. But I don't know if the Main._checkWorkspaces overriding should be inside this extension or be another standalone extension on which this one would depend. I mean, this could be an alternative for the people who are not at ease with the workspace collection ? At work, many of my colleagues have a workspace for every distant machine, and some of them would be quite confused about these shuffling workspaces. Maybe we could use boolean options like 'auto-collect empty workspaces surrounded by non-empty ones' and 'auto-collect trailing empty workspaces' ? ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
Il giorno mer, 23/02/2011 alle 14.15 +0100, Thomas Bouffon ha scritto: Okay, so now we have the same version and it works for both of us. But I don't know if the Main._checkWorkspaces overriding should be inside this extension or be another standalone extension on which this one would depend. I mean, this could be an alternative for the people who are not at ease with the workspace collection ? At work, many of my colleagues have a workspace for every distant machine, and some of them would be quite confused about these shuffling workspaces. That seems to be a sweet option. I think that the auto workspace management is not a suit everybody solution. It seems slick for people not used to workspaces, however *I* think that people accustomed to them will have a hard time with the auto collection shiftness. Maybe we could use boolean options like 'auto-collect empty workspaces surrounded by non-empty ones' and 'auto-collect trailing empty workspaces' ? Again sounds good, even though I think that just preserving all the workspaces but the trailing ones (as it is now) is a good replacement for old styled users :) Is there other feedback on this? I really have no idea whether it is me and you or the new behaviour is critical also for other users. Alessandro ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
That seems to be a sweet option. I think that the auto workspace management is not a suit everybody solution. It seems slick for people not used to workspaces, however *I* think that people accustomed to them will have a hard time with the auto collection shiftness. I'm not sure it's a problem of being able to get used to it. When you have more than 10 windows opened, you need some static organization. Maybe we could use boolean options like 'auto-collect empty workspaces surrounded by non-empty ones' and 'auto-collect trailing empty workspaces' ? Again sounds good, even though I think that just preserving all the workspaces but the trailing ones (as it is now) is a good replacement for old styled users :) I don't know, adding options is not that hard, and since we're customizing and already out of bounds, why not being able to tune a little more ? I was also thinking of a default number of workspaces at startup [?]. Is there other feedback on this? I really have no idea whether it is me and you or the new behaviour is critical also for other users. I don't know, I cannot afford time to install the current gnome-shell on my colleagues computers. Maybe on the next coffee break ? Cheers, Thomas 1B2.png___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
Il giorno mer, 23/02/2011 alle 10.28 +0100, Thomas Bouffon ha scritto: Hi ! Actually you can override the Main._checkWorkspaces function. I modified it so that it only removes the last workspaces if there are more than one. Thus if the first workspace is empty but the 2nd one is not, the 1st won't be deleted. I also modified _ensureAtLeastWorkspaces to move the window to the new workspace created, so that new workspaces are not collected if there are more than 2. This workflow suits my needs, at least (I generally use 4 Desktops and put Firefox on the 3rd, which now guarantees me the 4 desktops.) I renamed extension.js to extension.txt and attached it here. Any remarks are welcome ! It suits my workflow as well, so it was definitely welcome, and it makes sense in the context of the extension. Pushed to master, thanks a lot! Giovanni ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
It suits my workflow as well, so it was definitely welcome, and it makes sense in the context of the extension. Pushed to master, thanks a lot! Giovanni Hi Giovanni ! Thanks for both pushes ! What do you think of spliting the workspace management part of the extension ? Cheers, Thomas ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
Hi ! Thanks for adding this extension in the repo ! Unfortunately, I cannot build gnome-shell anymore, and I removed the previous install. So I'm stuck on 2.31 at the moment. As for the settings, is there a standard gui for gsettings ? If not, would a small python dialog box do the trick ? Something like a list display where one can add/remove lines, and then, when confirmed, starts the appropriate gsettings command ? Cheers, Thomas ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
Hi! As for the settings, is there a standard gui for gsettings ? If not, would a small python dialog box do the trick ? Something like a list display where one can add/remove lines, and then, when confirmed, starts the appropriate gsettings command ? The tool is called dconf-editor and is probably broken depending on the version you use. But feel free to write a more specialed python script of course. Regards, Johannes ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
Hi! I just tried dconf-editor for 2.31 (the latest is building, thanks to your advice) It looks a lot like gconf-editor. What should be the default behavior ? Should any user be aware of that utility, or should a custom utility write gsettings from a dialog box ? Will dconf-editor be the default app to manage gnome-shell settings ? Perhaps it would be nice to have a gnome-shell section in the main System settings (gnome-control-center), and manage extensions gsettings from there. No. Basically any interesting settings will be in System Settings but I doubt there will be an extra panel for gnome-shell, it will just be integrated where useful. However, as of now, extensions are not seen as part of the default user-experience and as such won't be presented to ordanary users in the system settings. And you now, everybody like killing settings... Rumors are that people are working on a TweakUI like utility that will contain common advanced settings for people wanting more customization but as not even a prototype has appeared yet it doesn't seem to happen in the 3.0 timeframe (but maybe 3.2). Vincent??? Regards, Johannes ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
No. Basically any interesting settings will be in System Settings but I doubt there will be an extra panel for gnome-shell, it will just be integrated where useful. However, as of now, extensions are not seen as part of the default user-experience and as such won't be presented to ordanary users in the system settings. And you now, everybody like killing settings... Rumors are that people are working on a TweakUI like utility that will contain common advanced settings for people wanting more customization but as not even a prototype has appeared yet it doesn't seem to happen in the 3.0 timeframe (but maybe 3.2). Vincent??? Ok, we'll stick with dconf-editor at the moment. But I have a little, slightly off-topic remark, at the moment : Having something which default experience is classy out of the box should not require killing settings, just adjusting them well by default. What's so bad about wanting to adjust stuff ? It would be really too bad to have a tweakui outside the shell : it would only be able to tune stuff that the shell allows it to tune, i.e. not much at the moment. It is quite odd having set up such an extension system and, afterwards, having to set their settings in something external which is outside the Shell experience ? I would like so much to have a Shell settings inside the control panel ! Don't get me wrong, I really like the gnome-shell experience, but I'm puzzled by the loss of adjustability I feel compared to gnome 2 (not to mention Compiz...). Cheers, Thomas ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
Il giorno dom, 20/02/2011 alle 00.16 +0100, Alessandro Crismani ha scritto: Il giorno sab, 19/02/2011 alle 19.02 +0100, Giovanni Campagna ha scritto: Il giorno lun, 07/02/2011 alle 22.04 +0100, Alessandro Crismani ha scritto: Il giorno lun, 07/02/2011 alle 10.21 +0100, Thomas Bouffon ha scritto: [...] I'm copy and pasting it here, it's not that long. It is a slightly modified version of your extension (renamed variables and minor edits, I rewrote it for learning purposes, hope you don't mind), that does not use Gconf (I planned to add class and titles and I wanted an easily modifiable config, so I'm directly using an array in the extension). Here it is, and it works with an up to today build (2.91.6): [...] That's the problem. I'm clueless about Gsettings and how to store into| use|abuse it. As usual, I should do a little bit of research, but I have yet to find an agreement with my to-do list :) I've taken the liberty to include your code in gnome-shell-extensions I browsed the repository and noted that I am listed as the original code in the metadata.json. The code I've mailed is a slightly modified paste of Thomas Bouffon's extension, so could you please credit him instead of me? :) I've added Thomas, but kept you as well, because you're work of adapting the extension to avoid using the overview code was very important in porting to 2.91.6. after some modifications to make it work with GSettings. Thanks very much for taking the effort to modify it and port it to GSetting, I'll try it as soon as I can. The extensions repo is a great idea, so is your work on it :) If you want to play with it, it is the auto-move-windows extension. The set of applications can be modified with: gsettings set org.gnome.shell.extensions.auto-move-windows application-list ['app-id.desktop:3'] (I'm using desktop files, obtained using ShellWindowTracker / ShellAppSystem, which are more reliable than window classes). You're example should roughly be gsettings set org.gnome.shell.extensions.auto-move-windows application-list ['rhythmbox.desktop:2','evolution.desktop:1','fedora-liferea.desktop:1'] Does your version work in the new workspace thumbnail Shell. My version failed due to auto management of workspaces. Let's say that I have only one workspace, and I want Rhythmbox on the third. I call the add_workspace_by_index twice, but the second added workspace is deleted because it is empty. Right now I am pinning the first four workspace, so they don't get deleted, but it is a ugly hack. Unfortunately, we cannot block the shell from collecting empty workspaces, so if the number of workspaces is greater than then the available, the application will end up on the last one. In my case it still works because I have 6 (5+1) workspaces available, which is enough for the applications I launch. Giovanni ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
Il giorno lun, 07/02/2011 alle 22.04 +0100, Alessandro Crismani ha scritto: Il giorno lun, 07/02/2011 alle 10.21 +0100, Thomas Bouffon ha scritto: [...] I'm copy and pasting it here, it's not that long. It is a slightly modified version of your extension (renamed variables and minor edits, I rewrote it for learning purposes, hope you don't mind), that does not use Gconf (I planned to add class and titles and I wanted an easily modifiable config, so I'm directly using an array in the extension). Here it is, and it works with an up to today build (2.91.6): [...] That's the problem. I'm clueless about Gsettings and how to store into| use|abuse it. As usual, I should do a little bit of research, but I have yet to find an agreement with my to-do list :) I've taken the liberty to include your code in gnome-shell-extensions, after some modifications to make it work with GSettings. If you want to play with it, it is the auto-move-windows extension. The set of applications can be modified with: gsettings set org.gnome.shell.extensions.auto-move-windows application-list ['app-id.desktop:3'] (I'm using desktop files, obtained using ShellWindowTracker / ShellAppSystem, which are more reliable than window classes). You're example should roughly be gsettings set org.gnome.shell.extensions.auto-move-windows application-list ['rhythmbox.desktop:2','evolution.desktop:1','fedora-liferea.desktop:1'] Giovanni ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
Il giorno sab, 19/02/2011 alle 19.02 +0100, Giovanni Campagna ha scritto: Il giorno lun, 07/02/2011 alle 22.04 +0100, Alessandro Crismani ha scritto: Il giorno lun, 07/02/2011 alle 10.21 +0100, Thomas Bouffon ha scritto: [...] I'm copy and pasting it here, it's not that long. It is a slightly modified version of your extension (renamed variables and minor edits, I rewrote it for learning purposes, hope you don't mind), that does not use Gconf (I planned to add class and titles and I wanted an easily modifiable config, so I'm directly using an array in the extension). Here it is, and it works with an up to today build (2.91.6): [...] That's the problem. I'm clueless about Gsettings and how to store into| use|abuse it. As usual, I should do a little bit of research, but I have yet to find an agreement with my to-do list :) I've taken the liberty to include your code in gnome-shell-extensions I browsed the repository and noted that I am listed as the original code in the metadata.json. The code I've mailed is a slightly modified paste of Thomas Bouffon's extension, so could you please credit him instead of me? :) after some modifications to make it work with GSettings. Thanks very much for taking the effort to modify it and port it to GSetting, I'll try it as soon as I can. The extensions repo is a great idea, so is your work on it :) If you want to play with it, it is the auto-move-windows extension. The set of applications can be modified with: gsettings set org.gnome.shell.extensions.auto-move-windows application-list ['app-id.desktop:3'] (I'm using desktop files, obtained using ShellWindowTracker / ShellAppSystem, which are more reliable than window classes). You're example should roughly be gsettings set org.gnome.shell.extensions.auto-move-windows application-list ['rhythmbox.desktop:2','evolution.desktop:1','fedora-liferea.desktop:1'] Does your version work in the new workspace thumbnail Shell. My version failed due to auto management of workspaces. Let's say that I have only one workspace, and I want Rhythmbox on the third. I call the add_workspace_by_index twice, but the second added workspace is deleted because it is empty. Right now I am pinning the first four workspace, so they don't get deleted, but it is a ugly hack. Alessandro ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
Hi Alessandro, Are you sure? I'm using it with an up to date Shell build, and if I open an app that has to go on the fourth workspace *from the terminal*, that workspace is created and the app moved there. Yes I am : if the extension has to create a workspace, gnome-shell crashes (I attached the terminal output in err.txt) Am I missing something or are you checking out the workspace-thumbnails branch? Could you please tell me what is not working in your setup, mine seems perfectly functional :) I'm building with the jhbuild script, so I guess, that's the regular branch. (version GNOME Shell 2.91.5). Maybe You modified some little bit in the extension which makes it work ? Can you post the js file, so that I can try it (You'll have to change the extension, as js files are refused by the mailing list) Beside, are you planning to ditch Gconf in the extension? I would like to store settings through Gsettings, I have also planned to add more features, like window class matching and geometry setting, but I never had the time to do it. I'm not that much of a planner, but if gsettings enables to use a nice gui for the settings, why not ? But I couldn't find much about how it works : gsettings stores info somewhere, but are these settings accessible through System settings ? I guess that once we master the settings management, we'll be able to start playing with the class/name/application, and being able to chose among these. Cheers, Thomas Gtk-Message: Failed to load module pk-gtk-module: libpk-gtk-module.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type Gtk-Message: Failed to load module canberra-gtk-module: libcanberra-gtk-module.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type Avertissement du gestionnaire de fenêtres : Log level 16: Accessibility: org.a11y.atspi schema not found. Are you sure that at-spi or at-spi2 is installed on your system? Avertissement du gestionnaire de fenêtres : Log level 16: Accessibility: invalid module path (NULL) Avertissement du gestionnaire de fenêtres : Log level 16: Accessibility: error loading the atk-bridge. Although the accessibility on the system is enabled and clutter accessibility is also enabled, accessibility support on GNOME Shell will not work JS LOG: GNOME Shell started at Mon Feb 07 2011 10:03:27 GMT+0100 (CET) (mutter:8491): GdmUser-WARNING **: Unable to load CK history: no seat-id found JS ERROR: !!! Exception was: TypeError: this.workspacesView is null JS ERROR: !!! lineNumber = '1117' JS ERROR: !!! fileName = '/home/tbouffon/gnome-shell/install/share/gnome-shell/js/ui/workspacesView.js' JS ERROR: !!! stack = '([object _private_Meta_Screen],[object _private_GLib_ParamSpec])@/home/tbouffon/gnome-shell/install/share/gnome-shell/js/ui/workspacesView.js:1117 ([object _private_Meta_Screen],[object _private_GLib_ParamSpec])@/home/tbouffon/gnome-shell/install/share/gjs-1.0/lang.js:110 @:0 FindAndMove([object _private_Meta_Display],[object _private_Meta_Window])@/home/tbouffon/gnome-shell/install/share/gnome-shell/extensions/workspace_...@gnome-shell-extensions.gnome.org/extension.js:29 ' JS ERROR: !!! message = 'this.workspacesView is null' JS ERROR: !!! Exception was: TypeError: this.workspacesView is null JS ERROR: !!! lineNumber = '1117' JS ERROR: !!! fileName = '/home/tbouffon/gnome-shell/install/share/gnome-shell/js/ui/workspacesView.js' JS ERROR: !!! stack = '([object _private_Meta_Screen],[object _private_GLib_ParamSpec])@/home/tbouffon/gnome-shell/install/share/gnome-shell/js/ui/workspacesView.js:1117 ([object _private_Meta_Screen],[object _private_GLib_ParamSpec])@/home/tbouffon/gnome-shell/install/share/gjs-1.0/lang.js:110 @:0 FindAndMove([object _private_Meta_Display],[object _private_Meta_Window])@/home/tbouffon/gnome-shell/install/share/gnome-shell/extensions/workspace_...@gnome-shell-extensions.gnome.org/extension.js:29 ' JS ERROR: !!! message = 'this.workspacesView is null' St-ERROR **: st_widget_get_theme_node called on a widget not in a stage aborting... Shell killed with signal 5 ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
missing workflows with gnome-shell
Hi, I tried the latest gnome-shell in the GNOME3 ISO put up Frederic Crozat and could not find equivalents for few workflows that used to work with the old GNOME. I searched the FAQ but could not find any solution and asking here to find solutions. Vertical workspace navigation: Currently all workspaces are in only one row. I want a fixed 3x3 number of workspaces. I keep my terminal in the centermost workspace where I spend most of the time. I keep browser, IRC, email client , all one workspace adjacent to the center workplace. This way, from the terminal, I can go to any workspace with just one keystroke. Imagine a big + sign, with my most active workspace in the center. However, with gnome-shell I am not able to find a way to navigate vertically nor does it remember the number of workspaces. Is there an alternate to this ? Keyboard Navigation: When I press the windows (super) key, I get a Windows, Applications tab. But neither arrow keys nor tab takes me to navigate across these two tabs. I am forced to use my mouse for navigating between these two. I have heard that gnome-shell is very keyboard friendly but I am not able to navigate across these two tabs via the keyboard. Any solution for this ? Hiding the panel: I always hide my gnome-panel using the direction buttons in the old gnome-panel. I set the panel to auto-hide also. This way I get maximum screen space for all my applications. However I am not able to find a way to hide the top panel in gnome-shell. How do I do it ? Please help me find alternatives for these workflows. Thanks. -- Sankar P http://psankar.blogspot.com ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
On 4 February 2011 08:49, Sankar P psan...@gnome.org wrote: Vertical workspace navigation: Currently all workspaces are in only one row. I want a fixed 3x3 number of workspaces. I keep my terminal in the centermost workspace where I spend most of the time. I keep browser, IRC, email client , all one workspace adjacent to the center workplace. This way, from the terminal, I can go to any workspace with just one keystroke. Imagine a big + sign, with my most active workspace in the center. However, with gnome-shell I am not able to find a way to navigate vertically nor does it remember the number of workspaces. Is there an alternate to this ? That's by design I believe. Workspaces in the shell are going to be created and removed on demand and the layout is going to be linear IIUC. But most of that work is still on branch[1]. Keyboard Navigation: When I press the windows (super) key, I get a Windows, Applications tab. But neither arrow keys nor tab takes me to navigate across these two tabs. I am forced to use my mouse for navigating between these two. I have heard that gnome-shell is very keyboard friendly but I am not able to navigate across these two tabs via the keyboard. Any solution for this ? Ctrl+Pg[Up|Down] Hiding the panel: I always hide my gnome-panel using the direction buttons in the old gnome-panel. I set the panel to auto-hide also. This way I get maximum screen space for all my applications. However I am not able to find a way to hide the top panel in gnome-shell. How do I do it ? Not possible currently. Not sure if that's been considered by the design people. Rui ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
2011/2/4 Rui Tiago Cação Matos tiagoma...@gmail.com: That's by design I believe. Workspaces in the shell are going to be created and removed on demand and the layout is going to be linear IIUC. But most of that work is still on branch[1]. [1] http://git.gnome.org/browse/gnome-shell/log/?h=workspace-thumbnails ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
Le vendredi 04 février 2011 à 10:21 +, Rui Tiago Cação Matos a écrit : Hiding the panel: I always hide my gnome-panel using the direction buttons in the old gnome-panel. I set the panel to auto-hide also. This way I get maximum screen space for all my applications. However I am not able to find a way to hide the top panel in gnome-shell. How do I do it ? Not possible currently. Not sure if that's been considered by the design people. I don't think designers will include this in the main design of the Shell, but writing an extension for that would be easy and I'm sure somebody will step in at some point. ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
2011/2/4 Milan Bouchet-Valat nalimi...@club.fr: Le vendredi 04 février 2011 à 10:21 +, Rui Tiago Cação Matos a écrit : Hiding the panel: I always hide my gnome-panel using the direction buttons in the old gnome-panel. I set the panel to auto-hide also. This way I get maximum screen space for all my applications. However I am not able to find a way to hide the top panel in gnome-shell. How do I do it ? Not possible currently. Not sure if that's been considered by the design people. I don't think designers will include this in the main design of the Shell, but writing an extension for that would be easy and I'm sure somebody will step in at some point. I really want to use gnome-shell moving forward. However, these things are kinda deal-killer for me. Are there any docs on how to write those extensions that you mentioned ? I can try my hands over the weekend. I believe fixed number of workspaces are something every developer will have. May be we should try to implement in the core instead of a plugin ? And one dumb question, should the plugins to gnome-shell also be written in JavaScript ? -- Sankar P http://psankar.blogspot.com ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
Le vendredi 04 février 2011 à 16:35 +0530, Sankar P a écrit : I really want to use gnome-shell moving forward. However, these things are kinda deal-killer for me. Are there any docs on how to write those extensions that you mentioned ? I can try my hands over the weekend. See http://live.gnome.org/GnomeShell/Extensions http://live.gnome.org/GnomeShell/Development And http://git.gnome.org/browse/gnome-shell-extensions for examples. I believe fixed number of workspaces are something every developer will have. May be we should try to implement in the core instead of a plugin ? I also feel like the Shell should allow people to have a fixed number of workspaces on start, while keeping the default behavior easy for most users. The problem is, it should not conflict with workspaces auto-management. See http://jimmac.musichall.cz/log/?p=1126 And one dumb question, should the plugins to gnome-shell also be written in JavaScript ? Yes. But that's really an advantage, not a constraint. Writing an animation to hide the panel will be much nicer in JS than it would have been with C. Not even speaking of coding, you only need to drop one .js file to install you extension, and you can try it live; with C, you'd have needed Autotools, make install, and building it each time you want to test it. Regar ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
Il giorno ven, 04/02/2011 alle 12.15 +0100, Milan Bouchet-Valat ha scritto: I believe fixed number of workspaces are something every developer will have. May be we should try to implement in the core instead of a plugin ? I also feel like the Shell should allow people to have a fixed number of workspaces on start, while keeping the default behavior easy for most users. The problem is, it should not conflict with workspaces auto-management. See http://jimmac.musichall.cz/log/?p=1126 An extension has been posted on this list some time ago that offers something similar. In particular, it allows opening different apps on a fixed workspace, which is if it doesn't exist (think of it as a sort of devilspie). I'm using and loving it right now, with a configuration that sounds like: Chromium: Workspace 1 Evolution: Workspace 2 Rhythmbox: Workspace 3 GTG: Workspace 4 Those apps are autostarted when I log in, and the extension creates the four workspaces and places them accordingly to the settings. If you only need a fixed number of workspaces at startup you may modify it to suit your needs. If you are interested search the archive of the list for the extension. I can't remember the topic, but I think it was posted by Thomas Bouffon, if I am not mistaken. Hope this helps you, Alessandro ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
On Fri, Feb 4, 2011 at 4:33 AM, Alessandro Crismani alessandro.crism...@gmail.com wrote: Il giorno ven, 04/02/2011 alle 12.15 +0100, Milan Bouchet-Valat ha scritto: I believe fixed number of workspaces are something every developer will have. May be we should try to implement in the core instead of a plugin ? I also feel like the Shell should allow people to have a fixed number of workspaces on start, while keeping the default behavior easy for most users. The problem is, it should not conflict with workspaces auto-management. See http://jimmac.musichall.cz/log/?p=1126 An extension has been posted on this list some time ago that offers something similar. In particular, it allows opening different apps on a fixed workspace, which is if it doesn't exist (think of it as a sort of devilspie). Yes, in fact you had posted a link to the extension some time back in November I believe. The link to the sample extension is: http://mail.gnome.org/archives/gnome-shell-list/2010-November/msg00036.html Compliments to Thomas Bouffon for his work. sri I'm using and loving it right now, with a configuration that sounds like: Chromium: Workspace 1 Evolution: Workspace 2 Rhythmbox: Workspace 3 GTG: Workspace 4 Those apps are autostarted when I log in, and the extension creates the four workspaces and places them accordingly to the settings. If you only need a fixed number of workspaces at startup you may modify it to suit your needs. If you are interested search the archive of the list for the extension. I can't remember the topic, but I think it was posted by Thomas Bouffon, if I am not mistaken. Hope this helps you, Alessandro ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
Re: missing workflows with gnome-shell
Hi, The name of the extension is workspace_win. But at the moment, I can't get it to create workspaces in the latest gnome-shell git version. It looks like it is not possible to create workspaces outside the overview mode. I'll try to have a look at it next week. And have it integrated in the extensions repo. Cheers, Thomas Le 4 févr. 2011 à 18:32, Sriram Ramkrishna s...@ramkrishna.me a écrit : On Fri, Feb 4, 2011 at 4:33 AM, Alessandro Crismani alessandro.crism...@gmail.com wrote: Il giorno ven, 04/02/2011 alle 12.15 +0100, Milan Bouchet-Valat ha scritto: I believe fixed number of workspaces are something every developer will have. May be we should try to implement in the core instead of a plugin ? I also feel like the Shell should allow people to have a fixed number of workspaces on start, while keeping the default behavior easy for most users. The problem is, it should not conflict with workspaces auto-management. See http://jimmac.musichall.cz/log/?p=1126 An extension has been posted on this list some time ago that offers something similar. In particular, it allows opening different apps on a fixed workspace, which is if it doesn't exist (think of it as a sort of devilspie). Yes, in fact you had posted a link to the extension some time back in November I believe. The link to the sample extension is: http://mail.gnome.org/archives/gnome-shell-list/2010-November/msg00036.html Compliments to Thomas Bouffon for his work. sri I'm using and loving it right now, with a configuration that sounds like: Chromium: Workspace 1 Evolution: Workspace 2 Rhythmbox: Workspace 3 GTG: Workspace 4 Those apps are autostarted when I log in, and the extension creates the four workspaces and places them accordingly to the settings. If you only need a fixed number of workspaces at startup you may modify it to suit your needs. If you are interested search the archive of the list for the extension. I can't remember the topic, but I think it was posted by Thomas Bouffon, if I am not mistaken. Hope this helps you, Alessandro ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list ___ gnome-shell-list mailing list gnome-shell-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-shell-list
