On Jul 13, 8:58 pm, Luke Maurer <[email protected]> wrote:
> On Jul 13, 5:19 pm, johnjbarton <[email protected]> wrote:
>
> > On Jul 13, 4:40 pm, Luke Maurer <[email protected]> wrote:
>
> > > I think you misunderstand. He needs it *active* for all the pages he's
> > > working with. But he hates having it *open* all the time. AFAIK, 1.4
> > > has no facility to have Firebug always *active* but *minimized* for
> > > all your pages.
>
> > Weren't you the one who was just saying you wanted Firebug off for
> > Gmail? You can not have "always active" and "off for Gmail". So I'll
> > assume you meant:
>
> I wasn't describing what *I* want but what IAmThatStrange wants. But
> nonetheless, here's what I want:
>
> * I want Firebug active for my site.
Ok open Fireubg for your site.
> * I want Firebug inactive for all other sites.
Ok don't open Firebug on any other site.
> * I want Firebug *visible* when it's visible and hidden when it's
> hidden. I'll bring it up when I want it and make it go away when I'm
> done with it. The console is just a damn window.
Ok toggle minimize with the statusbar icon;
>
> Now, despite your protestations, I *cannot* specify that I want
> Firebug active for my site. I can click the little bug to activate
> Firebug, and Firebug by a magical, invisible mechanism *beyond my
> control* will assume that I now want Firebug on for that site forever.
The mechanism is visible and under your control.
ON: Firebug status bar icon.
OFF: [(|)] Off icon in upper right corner.
This is deliberately asymetric to avoid accidental close.
> *IF* that's what I wanted, great, but any interface that quietly
> interprets minor actions as permanent decisions is going to be a pain
> in the ass. That misbehavior is compounded when you've redefined what
> the button on the far right of the title bar should do; now not only
> have you given a button surprising behavior, but - without telling the
> user! - you have made a permanent change to the user's preferences.
I'm sorry we redefined the upper right corner button.
> It's irritating enough to realize that you turned off debugging when
> you just meant to close the console; it's infuriating when it turns
> out that Firebug decided that you *also* wanted to turn off debugging
> for the entire site permanently.
It is not permanent; you can turn it back on at any time.
>
> And yes, if that happens, I can change it back. But why should I have
> to babysit Firebug? I've got shit to do, and the more my tools can get
> out of my way and just do what I thought I told them to, the better.
> In 1.3, I could just tell it what I wanted - on for this site, off for
> others, and that was that. Permanently. Whatever I did to close the
> console or open the console *or even suspend Firebug temporarily,* it
> just freaking did what I'd told it to.
I am confident that you will quickly learn to avoid hitting "off". Yes
its too bad we redefined that button. But the world is not going to
end really.
The Firebug status bar icon is larger and since it is a toggle you can
quickly move between minimize/unminize.
The key binding F12 also minimize/unminize, very convienent.
>
> Plus, 1.3 didn't try to be clever about when to be visible or not. I
> don't want it popping up unbidden, ever. Do you really want Firebug to
> join the UI Hall of Shame with that MS Office paperclip? I mean, you
> could close that too when it popped up. That doesn't mean it didn't
> piss people off royally.
I will be happy to agree with you: 1.3 was not too clever.
jjb
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---
