forked from L-four/multiple-monitor-panels
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix workspace overview overlap, add support for move icons and config…
…urations
- Loading branch information
Showing
10 changed files
with
758 additions
and
28 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
*~ | ||
TODO |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,19 @@ | ||
multiple-monitor-panels | ||
======================= | ||
## Multiple Monitor Panels | ||
|
||
Gnome-shell extension that adds panels including AppMenu to each additional monitor. | ||
Gnome-shell extension that adds top panels including a monitor specific AppMenu to each additional monitor. It also provides support for moving icons/widgets that are created by other extensions onto the secondary monitor. | ||
|
||
![](http://i.imgur.com/nUuBc.png) | ||
|
||
### Install: | ||
One Click Install via [extensions.gnome.org](https://extensions.gnome.org/extension/323/multiple-monitor-panels/) | ||
|
||
### Icon Moving Support: | ||
For Icon moving to work, it requires that the extension adds icon/widget to the panel using the Panel.addToStatusArea API. In the case the extension does not do this, its possible to fake support by adding a reference to the panel. It requires adding the following 2 lines to that extensions. | ||
|
||
enable(): | ||
Main.panel._statusArea.extensionName = [PanelMenuButton object]; | ||
disable(): | ||
Main.panel._statusArea.extensionName = null; | ||
|
||
### Author: | ||
[darkxst](https://github.com/darkxst) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,68 @@ | ||
/* -*- mode: js; js-basic-offset: 4; indent-tabs-mode: nil -*- */ | ||
|
||
const Gettext = imports.gettext; | ||
const Gio = imports.gi.Gio; | ||
|
||
const Config = imports.misc.config; | ||
const ExtensionUtils = imports.misc.extensionUtils; | ||
|
||
/** | ||
* initTranslations: | ||
* @domain: (optional): the gettext domain to use | ||
* | ||
* Initialize Gettext to load translations from extensionsdir/locale. | ||
* If @domain is not provided, it will be taken from metadata['gettext-domain'] | ||
*/ | ||
function initTranslations(domain) { | ||
let extension = ExtensionUtils.getCurrentExtension(); | ||
|
||
domain = domain || extension.metadata['gettext-domain']; | ||
|
||
// check if this extension was built with "make zip-file", and thus | ||
// has the locale files in a subfolder | ||
// otherwise assume that extension has been installed in the | ||
// same prefix as gnome-shell | ||
let localeDir = extension.dir.get_child('locale'); | ||
if (localeDir.query_exists(null)) | ||
Gettext.bindtextdomain(domain, localeDir.get_path()); | ||
else | ||
Gettext.bindtextdomain(domain, Config.LOCALEDIR); | ||
} | ||
|
||
/** | ||
* getSettings: | ||
* @schema: (optional): the GSettings schema id | ||
* | ||
* Builds and return a GSettings schema for @schema, using schema files | ||
* in extensionsdir/schemas. If @schema is not provided, it is taken from | ||
* metadata['settings-schema']. | ||
*/ | ||
function getSettings(schema) { | ||
let extension = ExtensionUtils.getCurrentExtension(); | ||
|
||
schema = schema || extension.metadata['settings-schema']; | ||
|
||
const GioSSS = Gio.SettingsSchemaSource; | ||
|
||
// check if this extension was built with "make zip-file", and thus | ||
// has the schema files in a subfolder | ||
// otherwise assume that extension has been installed in the | ||
// same prefix as gnome-shell (and therefore schemas are available | ||
// in the standard folders) | ||
let schemaDir = extension.dir.get_child('schemas'); | ||
let schemaSource; | ||
if (schemaDir.query_exists(null)) | ||
schemaSource = GioSSS.new_from_directory(schemaDir.get_path(), | ||
GioSSS.get_default(), | ||
false); | ||
else | ||
schemaSource = GioSSS.get_default(); | ||
|
||
let schemaObj = schemaSource.lookup(schema, true); | ||
if (!schemaObj) | ||
throw new Error('Schema ' + schema + ' could not be found for extension ' | ||
+ extension.metadata.uuid + '. Please check your installation.'); | ||
|
||
return new Gio.Settings({ settings_schema: schemaObj }); | ||
} | ||
|
Oops, something went wrong.