put tab close button on the same side as window close button

[Danielle Foré]

Marlin should (like Midori) put the tab close button on the same side as the window control button. So if your window close button is on the left, the tab close button should be on the left.

[ammonkey (am-monkeyd)]

hum we change the tabs close buttons now? what about the others applications? wouldn't it be better to have a gtk patch for this? instead of having to patch every app one by one?

The position of the button is defined in a metacity gconf key actually, yeah read me gconf. It's dropped in gnome-shell/mutter. Compiz/unity still use the gconf key. I am just wondering who gonna port this code to dconf (libmetacity). I am just wondering of the future of this functionality.

[Danielle Foré (danrabbit)]

If such a thing was possible, yes it'd probably be the optimal solution. The only problem is how do you know when the notebook is being used for static or dynamic tabs? It's one widget being used for two purposes. Ideally we'd want two separate widgets so that we could built a lot of functionality into a stock tabbar widget.

It's not only defined in gconf, it's also defined in your theme. I can't remember the name of the file right now, but you can check Midori to see where exactly it pulls that information from.

[ammonkey (am-monkeyd)]

At least we should have a widget in a common lib used by all elementary projects. This would avoid to write the same components and patch each appplications one by one.

The problem is such a library don't exist. Granite is a Rube Goldberg machine (in other word it's an overcomplicated library for nothing) builded by one man who decide which object are public which are private without any community consent. To cite a few exemple of my current frustations about this library:
  - Basics operations that u could do easily with glib are a nightmare or just not possible (cf g_setting_bind).
  - GApplication can have many different behaviors while the abstraction Granite.Application force u to use what his maintainer in his good will has choosen for you.
  - Even in the About dialog u can't write what u really want.
  - etc etc etcetera ...

Anything and everything end up in this library the best like the worst coupled with the useless. Personaly i am kind of tired to fight with MBarvian about this library. I refuse to use this library in any of my project. So i guess it's a dead end.

[Danielle Foré (danrabbit)]

Then this is probably something we need to bring up (either in a blueprint or a series of bug reports or at a Council meeting) and resolve. I do agree that it's counterproductive for us to write the same code over and over again and we should have a library that contains things like this. Granite is supposed to be that library.

[xapantu (xapantu)]

Now, there is a ML, please subscribe to discuss about granite future
development, I am sure that we can fix and improve it.

[Timo Reimerdes (timorei)]

So - is there a way to pick the side of the tab close button, or isn't there? I'm taking the current branch from lp compiled with ./configure --prefix=/usr --enable-gtk3 --disable-addons and am deeply impressed - so much, I'll test it as default browser (currently in gnome-shell, hopefully soon in pantheon) for now.

It's the only application that I am aware off that has the tabs close buttons on the left and I simply cannot find a working change.

(There really needs to be an easier way to find information like that... and be it about:config pages or something as bad)