Linked by David Adams on Tue 14th Feb 2012 17:25 UTC, submitted by Anonymous
Ubuntu, Kubuntu, Xubuntu It looks like a new "locally integrated menu" will make it into Unity, starting with version 5.6.0. There's basically no information about the new locally integrated menubar, except for two bug reports which link to some custom Unity, Compiz, Metacity and Light Themes branches so to see "LIM" in action, I've compiled all these branches and here's the result. The "locally integrated menubar" can be displayed on the panel (for maximized windows) as well as in the window decoration (unmaximized windows). But it's not displayed on both in the same time.
Permalink for comment 507253
To read all comments associated with this story, please click here.
RE[4]: Quo Vadis, Canonical?
by Neolander on Wed 15th Feb 2012 13:24 UTC in reply to "RE[3]: Quo Vadis, Canonical?"
Member since:

I agree that one UI per device could be a solution, if one-size-fits-all proves to be impossible to implement.

What I don't understand is when UI toolkits seem to become incompatible with certain input devices on purpose.

See the paragraph here as an example :

It is said that Wacom tablets are not compatible with Windows 8's Metro interface because their drivers do not generate touch events. Seriously, how does this make any sense ? How much would it cost Microsoft to just support a generic "pointer" abstraction instead of forcing drivers to mimick touch when they actually abstract something totally unrelated ?

I can understand having one UI per device family, but not one toolkit per device.

PS : Sorry if my posting style is a bit aggressive today. I've been dealing with some ugly flu/cold/whatever that prevents me to breathe and sleep properly for a few days now, and it starts to show.

Edited 2012-02-15 13:30 UTC

Reply Parent Score: 1