On Jul 1, 8:52 pm, whatcould <da...@whatcould.com> wrote:
...
> 2. The other issue is the X button. I'm sure I'll get used to it
> eventually, but there's some big cognitive dissonance going on with
> the X (close) button and the Firebug icon. I know now that clicking
> the X _disables_ fb, and clicking the bug icon just hides it. But that
> was not immediately apparent, and I'm having a hard time teaching
> myself the new behavior. I have the feeling that we expect the
> opposite to be true -- clicking the bug enables FB, so clicking the
> bug again would disable it, right? [nope]. And the X says to me,
> "close this interface", not, "disable firebug".
But you are focusing on the first experience of a 1.3 user. Consider
the routine experience of a 1.4 user or a new 1.4 user.
The first use of the Firebug icon activates the page *and* shows the
UI. The 2nd click hides the UI, 3rd shows, 4th hides....
So the Firebug icon allows you to peek at the page without the UI in
the way. This is a huge win for designers especially. If we use this
button for deactivation, then we lose it for hide (minimize). I think
that is not a good tradeoff.
Deactivation is destructive: all of the console/script/net panel data
will be erased. That ought to be harder, for the same reason we have
to endure those awful confirm on delete dialogs.
If you are using firebug on a page, the chances are that you won't
close Firebug at all until you want to test the page without Firebug.
So during most of your development you will close the whole tab rather
than closing Firebug.
jjb
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to firebug@googlegroups.com
To unsubscribe from this group, send email to
firebug+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---
