In the last few weeks( since the initial commit of this project ), I have used this work to propel my study and use of
-
javascript
andgjs
, a gnome javascript interpreter for the gnome shell -
git
and [https://github.com] to track this code Projects -
atom
and many packages the text editor -
Clutter
,St
, andGtk
-- various APIs and components to interact with gnome-shell and this extensions
-
See about changing the perspective of the stage, a new stage, or putting all the sector imagery inside another container so that when the sector imagery is drawn off of center, the prallax visual cues (though it is cool, and I hope to use) can be avoided or controlled.
-
11-22 Get a keybinding
-
11-23,11-24Get a full screen window
-
Learn how to draw on the window [11-26] See the commit.
-
11-22load favorites from gnome ?
-
[11-30 - 12-2] save preferences so we can make our own menus
-
start working with glade to make the prefs menu more accessible -
11-30icons for menus?
-
Make up some default stuff for myself, ssh commands, hue commands, getCurrentExtension
-
learn tweener
-
Use logger.js (perhaps rather than my own?)
A lot of these are in the code at the moment for references, but they will at some point be removed, so I wanted to keep them around.
- https://wiki.gnome.org/Projects/GnomeShell/Extensions/StepByStepTutorial This one really is the one that got me going on this thing. It seems a bit out-dated, but it was a great springboard
- https://wiki.gnome.org/Projects/GnomeShell/Extensions/Writing Another good oveerview
- https://wiki.gnome.org/Projects/GnomeShell/Extensions Reference material
- https://gitlab.gnome.org/GNOME/gnome-shell/blob/master/js/misc/extensionUtils.js This is something I ran across that taught me a new syntax for imports. I like it better as it is more concise.
- I've had quite a bit of learning to do. I've started using
git
and reading a lot of other extension code to help with developing ideas and understanding. - I now know what a snippet is (and how to use them in atom)
- I got a couple of nice packages for atom, and I'm still working on (thinking about) developing my own.
- [fold-navigator][https: //atom.io/packages/fold-navigator]
- fold-navigator [^1][https://atom.io/packages/fold-navigator]
- Would like for it to be less distracting as it changes width from file to file.
bluetoothctl
is nice to connect to saved devices automatically. Already working on some scripts.
amp
connects to the amp via bluetooth with the simple command bluetoothctl connect 3C:91:80:11:AF:2D
The only hard thing to remember is the address.
I used hidetopbar as a model to discover the Main.wm.addkeybinding method
Able to get a list of favorite apps from gnome shell. Now working on how to run one from the list. Using the extension Panel_Favorites for help here.
It seems that the key I was missing was Main.uiGroup.add_actor()
to display the content I was trying to create. (Now I get to try to make my content). Also, after reading more source, it seems that it really should be Main.layoutManager.uiGroup.add_actor()
I stumbled across [https://unix.stackexchange.com/questions/388238/how-to-set-super-windows-key-to-show-all-applications-menu-in-gnome-de]
And with few a more tweaks, I can now bind the shortcut to the lone <Super_L>
key! I have a few more questions, like why gsettings set|get
doesn't see the extensions path org.gnome.shell.extensions.*
where all the extensions schemas are held. There is a little hack, though: I can't specifically set my extension to the <Super_L>
key, but I can set
gsettings set org.gnome.shell.keybindings toggle-overview "['Super_L']"
Then, inside the extension code, we can use
setCustomKeybindingHandler(
'toggle-overview',
ShellActionMode.ALL,
this._keyAction.bind(this))
to set the key handler to our own extension code.
More to come.