On Jul 1, 2:32 am, HIghway of Life <[email protected]> wrote:
> Hi John, thanks for the reply.
>
> I read through the blog post, but I'm no closer to finding a good
> solution for working with the new model -- only that it will cause
> slow-downs in my normal workflow (and from reading other topics, it's
> obviously caused a lot of frustrations from others over the same
> issue).
>
> In the previous model, it was possible to enable Firebug only for the
> domains I needed it enabled for, all other browsing of websites was
> not affected. It remained closed while active on that domain so that
> it could catch any firebug logging or errors that would occur. While
> browsing the domains I am working on development for, if an error
> crops up, I catch it, I don't have to remember to turn Firebug on for
> my session, or enable it for all web pages, which takes a huge hit on
> the performance. If I forget to enable Firebug, I could miss these
> errors.
Still true in Firebug 1.4. The only difference is the UI. In 1.3 you
have to open the permissions panel and add domains manually. In 1.4,
you just open Firebug on the site the first time you need it.
>
> In the old model, clicking the (x) hide your panel, now it deactivates
> the panel and you have to go through all the steps required to
> reactivate your settings. It's not intuitive that (x) means disable
> Firebug. And especially since that exact button did something
> completely different in Firebug 1.3 that everybody got used to.
Clicking the [X] closes Firebug. That is pretty standard user
interface. For example it is used in every application on Windows,
Linux, and Mac. (Well of course Mac uses a circle rather than a
square, as they would).
>
> You don’t have to please everybody by appeasing the 'vast majority',
> but it would seem to me that if you have a vast number of users, each
> of whom have a different preference, that control over that preference
> should be paramount.
Which "vast" are you talking about? The dozen or so folks who have
posted here about 1.4? Or the dozen or so folks who complained about
1.3? Really we can't use newsgroup posts as a proxy for votes. What we
can to is try to make the tool work very well. The key to that is
concrete, specific, detailed descriptions rather than "make it work
like it used to".
> 1.4 has simply taken the control away from the users over how they
> wish Firebug to be active and enabled. If it were not for the speed of
> Firefox 3.5 and Firebug 1.4, I would switch back to Firefox 3.0 just
> so I could have the old activation model back.
>
> In the various topics on this discussion forum, there are 4 topics
> full of disappointed users with the new activation model. Of the
> responses in those topics including the feedback topic, 72% of the
> users either hated or were disappointed with the new model. 12% liked
> the new model, and 16% were indifferent.
Yes, but you are taking 72% of a tiny fraction of all Firebug users.
We had about 8,000 beta users, so even if 40 people here did not like
it, 40/8000 is only 0.5%, so we have 99.5% satisfied users. Do you
buy that? Me neither, so let's give up trying to count people who
complain.
>
> I'm really hoping Firebug will go back to the old model, or have some
> kind of combination between the two models because I understand why it
> was changed, but I do not think it was a good change for a lot of
> people. - I would really hate to have to install a plugin to get the
> desired functionality that already existed in a previous version.
It is possible that someone will come along to work on Firebug and
want to work on the activation. Possible but unlikely.
>
> There may also be bugs here that are causing much of the annoyance as
> well.
> E.g.: when you enable firebug, your subsequent pageload (not refresh)
> will usually load with Firebug disabled, and clicking on the Firebug
> icon is required to activate Firebug again, at which time it will
> remain active.
? I don't understand what you are saying. What is "pageload"?
> Shutting down Firebug, the subsequent page load will not only
> reactivate Firebug, but open the Firebug window as well. Requiring you
> to shut it down a second time.
? What will work much better is to describe the actions in terms of
the user interface, a single step at a time, eg:
1) Click the red [X] box in the upper right, Firebug UI disappears.
2) ...
> The third thing is the (x) causing Firebug to shut down unexpectedly
> for all the users who were used to the functionality of Firebug 1.3
[x] closes Firebug as I explained. What else would it do?
>
> Thanks again for your time and work on Firebug. :)
You're welcome!
> - Highway of Life
> Software Engineer
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
