On Aug 5, 11:50 am, Jon <[email protected]> wrote:
> I've been through a dozen of these posts about 1.4's UX (wherein I
> learned that the developer takes quite an attitude toward
> "complainers," "whiners," and layabout do-no-gooders, so I'll expect a
> witty retort that the developer's been through millions of them). I
There are two Firebug developers who reply here. I do not recall ever
saying "whiners" etc. I may have used the word "complainer", but I
meant it to describe someone with a complaint.
I value the input from concerned users. That is different from
agreeing with their demands.
> wholeheartedly agree with the points above. I'll make a bullet list
> of wishes, since I want you to know I take this seriously and I'm not
> a "whiner". Also I hope to be listened to. I generally love Firebug
> and have written emails complimenting it, and I have thanked the devs
> for their hard work and a great useful tool. So here we go:
>
> - Lose the "on/off" functionality. *Since this is an add-on* the
> close button shouldn't "quit", or change settings in the background,
> etc etc. Want to quit Firebug? Tools->Add-ons->Disable.
You don't have to click the Off button. Many people don't agree with
you.
>
> - Go back to the old "visible/invisible paradigm" rather than the new
> "off/minimize" paradigm. Call what you now consider the "Minimize"
> button's functionality the "Close" button. The "minimize" feature is
> superfluous if the "close" button does what any other addon's "close"
> button does, which is disappear (but continue to work for us when we
> need it in a few minutes.)
We've been through this. Others disagree. I am now determined not to
reopen this issue.
>
> - Firebug should run all panels, by default, for any domain, on any
> web page, on any tab. We can always set the preferences to "disable
> for all pages" or "enable for all pages"
That fits your style of development. It does not fit everyone.
Enabling all of the panels is a simple one time operation. We have no
plans to change this.
>
> - The Net tab should show me all the requests that have been going on
> before I displayed firebug, that means what happened while minimized,
The Net panel will show you all traffic that occurs when FIrebug is
minimized.
> without refreshing the page. I thought this was the way it worked
> before which is why I'm surprised we need to refresh now. Did it not
You have to refresh the first time you open Firebug on a page. That
has always been true. In 1.3 Firebug just refreshed without asking.
> work that way before? Regardless, Firebug should always have been
> paying attention. The resources are minimal to do this and un-
> streamlining the add-on to gain 20K of resources is a poor trade.
The resource in you case may be minimal. Its not true generally.
> - You seem to be convinced that people need to get used to new button
> placement even if they were poorly placed to begin with. You can
> categorize the interface as mimicking a standalone application
> (minimize restore and close, _ [] X), but you can also categorize this
> as an addon with its own rules as before - Plus if you keep moving
> buttons around and you piss off your current users simply to gain
> (millions of brand new???) users.
I already apologized for moving the buttons. I have no plans to make
that mistake again any time soon.
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
-~----------~----~----~----~------~----~------~--~---
