On Fri, Jul 15, 2011 at 3:08 PM, Artur Wroblewski wrote:
> On Fri, Jul 15, 2011 at 5:25 PM, Jasper St. Pierre
> wrote:
> > On Fri, Jul 15, 2011 at 11:55 AM, Federico Mena Quintero
> > wrote:
> [...]
> >> - Gnome-shell wants to have a coherent design. Still, it needs to
> >> accept that not ever
On Fri, Jul 15, 2011 at 5:25 PM, Jasper St. Pierre
wrote:
> On Fri, Jul 15, 2011 at 11:55 AM, Federico Mena Quintero
> wrote:
[...]
>> - Gnome-shell wants to have a coherent design. Still, it needs to
>> accept that not everyone's needs are equal.
>
> It doesn't need to.
Is above nice try to st
On Fri, Jul 15, 2011 at 11:55 AM, Federico Mena Quintero wrote:
> On Thu, 2011-07-14 at 13:54 -0400, Jasper St. Pierre wrote:
>
> > They're three separate actors by design, because it's *really hard* to
> > do it otherwise. I assume what you really want is a method or
> > something that will hide
On Thu, 2011-07-14 at 13:54 -0400, Jasper St. Pierre wrote:
> They're three separate actors by design, because it's *really hard* to
> do it otherwise. I assume what you really want is a method or
> something that will hide all three for you. I doubt you're going to
> get that API: it doesn't real
2011/7/14 Artur Wroblewski
> On Thu, Jul 14, 2011 at 11:06 AM, Florian Müllner
> wrote:
> > 2011/7/14 Artur Wroblewski
>
> [...]
> >>
> > (Yes, we could hide the corners "automagically" when the main panel actor
> is
> > hidden, but the panel is *supposed* to be always visible)
>
> Not accordin
On Thu, Jul 14, 2011 at 2:08 PM, Artur Wroblewski wrote:
> On Thu, Jul 14, 2011 at 11:06 AM, Florian Müllner
> wrote:
> > 2011/7/14 Artur Wroblewski
>
> [...]
> >>
> > (Yes, we could hide the corners "automagically" when the main panel actor
> is
> > hidden, but the panel is *supposed* to be alw
On Thu, Jul 14, 2011 at 11:06 AM, Florian Müllner wrote:
> 2011/7/14 Artur Wroblewski
[...]
>>
> (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 p
On Thu, Jul 14, 2011 at 6:54 PM, Jasper St. Pierre
wrote:
>
>
> On Thu, Jul 14, 2011 at 1:46 PM, Artur Wroblewski
> wrote:
>>
>> On Thu, Jul 14, 2011 at 9:10 AM, Jasper St. Pierre
>> wrote:
>> >
>> >
>> > On Thu, Jul 14, 2011 at 4:00 AM, Artur Wroblewski
>> >
>> [...]
>> >> What's its other pur
On Thu, Jul 14, 2011 at 1:46 PM, Artur Wroblewski wrote:
> On Thu, Jul 14, 2011 at 9:10 AM, Jasper St. Pierre
> wrote:
> >
> >
> > On Thu, Jul 14, 2011 at 4:00 AM, Artur Wroblewski >
> [...]
> >> What's its other purpose? Why it does not hide whole
> >> panel (API (?), i.e. "panel._leftCorner" s
On Thu, Jul 14, 2011 at 9:10 AM, Jasper St. Pierre
wrote:
>
>
> On Thu, Jul 14, 2011 at 4:00 AM, Artur Wroblewski
[...]
>> What's its other purpose? Why it does not hide whole
>> panel (API (?), i.e. "panel._leftCorner" suggests that corners are part
>> of the topbar).
>
> The top panel and the c
2011/7/14 Artur Wroblewski
> I would really appreciate explanation why the code has to be so
> complex? IMHO, simple Main.panle.actor.hide should be intuitive
> enough. What's its other purpose? Why it does not hide whole
> panel (API (?), i.e. "panel._leftCorner" suggests that corners are part
>
On Thu, Jul 14, 2011 at 4:00 AM, Artur Wroblewski wrote:
> On Wed, Jul 13, 2011 at 11:40 PM, Artur Wroblewski
> wrote:
> > Any tips how to simplify the code above?
>
> Thanks to
>
> https://bugzilla.gnome.org/show_bug.cgi?id=654518
>
> I have the following code, which works
>
> ---
> const M
On Wed, Jul 13, 2011 at 11:40 PM, Artur Wroblewski
wrote:
> Any tips how to simplify the code above?
Thanks to
https://bugzilla.gnome.org/show_bug.cgi?id=654518
I have the following code, which works
---
const Main = imports.ui.main;
function _hidePanel() {
Main.chrome.removeActor(M
On Wed, Jul 13, 2011 at 1:55 AM, Florian Max wrote:
> 2011/7/12 Artur Wroblewski
>>
>> On Thu, Jun 2, 2011 at 10:26 AM, Florian Müllner
>> wrote:
>> It is quite worrying that simple Main.panel.actor.hide is
>> not enough. Why hackery involving subcomponents of
>> topbar is required? (I don't car
2011/7/12 Artur Wroblewski
> On Thu, Jun 2, 2011 at 10:26 AM, Florian Müllner
> wrote:
> It is quite worrying that simple Main.panel.actor.hide is
> not enough. Why hackery involving subcomponents of
> topbar is required? (I don't care about animations and
> so on)
>
That is because the panel s
On Thu, Jun 2, 2011 at 10:26 AM, Florian Müllner wrote:
> Hey,
>
> 2011/6/2 Artur Wroblewski
>>
>> good point. shouldn't some CSS suffice here, i.e. height: 0px or
>> visibility: none?
>
> No, that would only "hide" the panel background - without doing fancy stuff
> like animations, you'll need s
Hey,
2011/6/2 Artur Wroblewski
> good point. shouldn't some CSS suffice here, i.e. height: 0px or
> visibility: none?
>
No, that would only "hide" the panel background - without doing fancy stuff
like animations, you'll need something along the lines of:
Main.overview.connect('showing', functi
On Wed, Jun 1, 2011 at 6:45 PM, Patrick Michael Niedzielski
wrote:
> On mar, 2011-05-31 at 19:37 +0100, Artur Wroblewski wrote:
>> hi,
>>
>> how to remove the topbar?
>>
>> i am not talking about hiding it. i just want to get rid of topbar
>> as having it in activities mode is more than enough for
On mar, 2011-05-31 at 19:37 +0100, Artur Wroblewski wrote:
> hi,
>
> how to remove the topbar?
>
> i am not talking about hiding it. i just want to get rid of topbar
> as having it in activities mode is more than enough for me.
>
> is there an option for that? if not, is there a chance that a pa
hi,
how to remove the topbar?
i am not talking about hiding it. i just want to get rid of topbar
as having it in activities mode is more than enough for me.
is there an option for that? if not, is there a chance that a patch would
be accepted?
best regards,
w
__
20 matches
Mail list logo
