When OPTIONS.GROUP_BY_APP=false, nothing works.

[JamesSwift]

I don't really like having my windows grouped, so I tried to set OPTIONS.GROUP_BY_APP=false. But when I do, although it lists the windows, you can't switch between them, and for some reason the icons get much bigger. I'm a JS developer, and I was going to look into it, but I have no experience working with gnome at all and haven't the time to start debugging right now. Anyone else got a patch for this?

[slamora]

I'm affected for this bug too.

[siefkenj]

This is a feature I never had the time to re-implement properly :-(. ATM, I believe it tries to auto-expand all app groups, but the framework should be set up for a proper implementation. I believe that if you modify WindowListManager to add app buttons instead of AppGroups it will produce true non-grouping behaviour. To debug in Gnome, the key things to know are: Alt+f2 lg to start lookingglass where some errors are printed. Also, run gnome-shell --replace from a terminal to see a host of other error messages gnome-shell offers (some errors are only reported there). global.log is like console.log from web browsers. If anyone is willing to help with this, it'd be greatly appreciated as I am too busy for hacking lately...

[slamora]

@siefkenj I have taken a look, and I've found that the problem also appears when you select "Expand Group" at the right click of the window list.

[JamesSwift]

Can anyone tell me where the documentation for gnome extensions is? I've searched fruitlessly. It almost seems like gnome are actively trying to prevent people writing extensions. If I can get hold of the documentation I might have a poke around and see if I can fix this bug.

[siefkenj]

They aren't trying to prevent extension creation, but they do have a huge documentation problem...The best so far is probably http://mathematicalcoffee.blogspot.ca/2012/09/gnome-shell-javascript-source.html @mathematicalcoffee has started writing documentation for a lot of the gnome-shell components. Also, hanging out in #extensions on irc.gimp.org is pretty much essential while developing shell extensions.

[JamesSwift]

Thanks. If I get chance, I'll take a look. As I've never written a gnome shell extension before though, it might be quite a steep learning curve. Plus the fact that I'm currently running windows doesn't help.

You seem quite a fan of the let method of scoping variables. As it's not supported in all browsers (and I write WWW client-side code normally), I've avoided using it. Only recently discovered it in fact. Seems to have some interesting applications.

[siefkenj]

let is standard for all the gnome-shell components. It's nice in that it makes scoping...exist, like in other languages :-). The gnome javascript implementation is based off of SpiderMonkey, so you can use Mozilla javascript extensions if it makes your life easier. I think the core of gnome shell is only using let from es6, and waiting for the rest to be standardized before using it in the code. Lately though, I've been using coffeescript, which fixes a lot of the issues :-).

[JamesSwift]

Well, var scopes to the containing function (or global if it is in the global space). I suppose coming from PHP this just felt natural to me. But I see let definitely has some advantages, for loops for example.