Linked by Thom Holwerda on Mon 3rd May 2010 22:04 UTC
Ubuntu, Kubuntu, Xubuntu Remember how Mark Shuttleworth justified moving the window titlebar widgets to the left by claiming the space freed up on the right side could now be used for something else? On his blog, Shuttleworth unveiled what, exactly, Ubuntu's plans are: window indicators, or 'windicators'. In a nutshell, it comes down to having a tray area in every window.
Thread beginning with comment 422576
To read all comments associated with this story, please click here.
My take
by WereCatf on Tue 4th May 2010 05:51 UTC
WereCatf
Member since:
2006-02-15

I really do think having a standardized way of handling per-application volume, showing online/offline status etc is a really good idea: f.ex. controlling volume would then work exactly the same in every single application, in exactly the same place, and thus would be very easy to remember, not to mention that you'd only have to fix bugs in one single place and get the bug fixed in all the audio-using applications at once. So yes, props for a good idea.

Now, about the implementation? It seems to me that his idea for implementing this thing is a combination of theme engine and client-side modifications. Ugh, horrible idea; changing theme would break it immediately. If he on the other hand wanted to modify Metacity then this thing would become WM-dependant and would not work in any other DE!

I hope they re-think this thing and implement it in a way that can then easily be implemented in other DEs as well.

Reply Score: 3

RE: My take
by phoenix on Tue 4th May 2010 15:25 in reply to "My take"
phoenix Member since:
2005-07-11

I really do think having a standardized way of handling per-application volume, showing online/offline status etc is a really good idea: f.ex. controlling volume would then work exactly the same in every single application, in exactly the same place, and thus would be very easy to remember, not to mention that you'd only have to fix bugs in one single place and get the bug fixed in all the audio-using applications at once. So yes, props for a good idea.


Ah, but this would not be "handled all in one place". You have to modify every single client application to support this. This is all handled "inside the app". Which means, if you want to change 1 small detail about volume control you have to edit every single application that uses that volume control.

Compare this to host/server-side handling of window decorations: you make 1 change in 1 place, and every single window picks up the change.

What you want ... we already have. It's called a "window manager" for a reason.

I hope they re-think this thing and implement it in a way that can then easily be implemented in other DEs as well.


AKA, don't do it on the client side of things. Come up with a d-bus protocol for it, update the WMs to support it, and migrate apps to use the d-bus protocol with a fall-back to the current setup.

Reply Parent Score: 2

RE[2]: My take
by WereCatf on Tue 4th May 2010 20:40 in reply to "RE: My take"
WereCatf Member since:
2006-02-15

Ah, but this would not be "handled all in one place". You have to modify every single client application to support this. This is all handled "inside the app". Which means, if you want to change 1 small detail about volume control you have to edit every single application that uses that volume control.

You didn't really bother reading my comment, did you? I DID say I don't like their implementation, period. I said I like the general idea, ie. provide a standardized way for controlling such things.

Reply Parent Score: 2