Re: getting rid of topbar
- From: "Jasper St. Pierre" <jstpierre mecheye net>
- To: Artur Wroblewski <wrobell pld-linux org>
- Cc: gnome-shell-list gnome org
- Subject: Re: getting rid of topbar
- Date: Thu, 14 Jul 2011 14:59:15 -0400
On Thu, Jul 14, 2011 at 2:08 PM, Artur Wroblewski
<wrobell pld-linux org> wrote:
[...]
>>
> (Yes, we could hide the corners "automagically" when the main panel actor is
> hidden, but the panel is *supposed* to be always visible)
Not according to Jasper who wrote "and we hide/show the top panel
in certain cases". I assume the truth is somewhere in the middle here? ;)
It is somewhere in the middle. chrome.js sets the actor to be invisible when a window goes full-screen. That's it. Mutter already ignores struts constraints on a full-screen window, so it isn't necessary (and expensive for all the other windows) if we re-set the struts.
> Keeping in mind that your extension is doing stuff that is conflicting with
> the gnome-shell design, you cannot really expect a convenience API for that
> purpose; especially as there is literally an infinite number of stuff that
> is conflicting with the design, it would be impossible to provide a
> convenient API for any of those.
Well, not sure about the design principles. But I really do not want to
sacrify usability of my screen for something which purpose is "indentifiable
visual identity" (https://live.gnome.org/GnomeShell/Design).
> Or in other words: you want to do unsupported stuff, you'll need to jump
> through some hoops.
Question is. Can we improve the programming experience here? :) If not - why?
Programming is a mix of ugly hacks. I think realistically, we could change the name of "Panel.actor" so it's a little less deceiving, but that would break existing extensions and wouldn't really be worth the effort.
[...]
--
Jasper
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]