On Jul 1, 5:22 am, MorningZ <[email protected]> wrote:
> "Ok right away I see your problem. Does Visual Studio generates as a
> new file name every time? And it's not a web site so you don't even
> have a domain correct?"
>
> I have a local DNS entry so i am hitting a consistant domain
> name,www.oursite.com.local, which just points to 127.0.0.1 And studio
> opens up a new browser window, not a new file name
If the URL is the same, the page should be active. If not something is
broken.
>
> "Just to help the communications, we would not call that "up
> disabled".
> Rather we would say "closed" (because you have no UI) and "suspended"
> because the icon is gray. "
>
> You can call it what you want, i call it "not running right away and
> watching net traffic and logging to the console"...
If it is not active, you will get no logging or net traffic.
>
> "If you had ever done this in the past for that URL, Firebug would
> already be active. "
>
> No, no it wouldn't if it was a new browser window
The new browser window has nothing to do with activation. The active
URL are stored as page annotations in Firefox database.
>
> "I like "undock" but we call it "detach". If you had been detached
> before, you would stay detached"
>
> OK, "detached", my bad.... again, this doesn't happen for new browser
> windows
That part I would consider to be a design bug and could be fixed.
>
> "From what I can see in your information so far, the issue here is
> that
> Visual Studio is generating file name"
>
> As mentioned above, you do not have this correctly... Studio opens up
> a new browser window..... and look, you're not understanding what
> the core of the issue:
> - When a new browser window opens up on my local site here (or any
> site i "white list" like 1.3 allowed), i would like Firebug to be
> running/watching/enabled/activated/whatever-other-term-goes-here, and
> not have to go through clicking, detaching, and dragging stuff out of
> my way on a constant basis
I just did the following test:
1) Open Firefox on http://getfirebug.com
2) Open Firebug
3) Exit Firefox
4) Open Firefox on http://getfirebug.com
Firebug is now open. I did not click additional buttons.
>
> "So it's not possible to anticipate all the cases"
>
> But you guys already have! It's called "the way 1.3 worked".. if you
Ok, but now we have 1.4. So let's concentrate on what we can do.
> just combined the two, you'd probably cover 98% of the use cases
There's that percentage thing again. It's not helpful since we have no
way to measure it.
>
> "As a practical matter, I am personally not going to re-work the
> activation mode"
>
> I haven't seen one person say scrap it and start over, we're looking
> for a layer on top that when the decision is made by Firebug: "Am I
> activated?", that it checks a user-defined list of domain names to be
> part of the decision... if it's starting up for the first time, check
> the list to start activated
We are ready to help anyone who wants to write and maintain such code.
>
> sir_brizz's post above this one makes the point just like I am trying
> to make:
>
> "This way I never had to wonder if, for example, Firebug was running
> on ANY of my development sites (all on the same domain). With only
> slight modifications, this activation model could have easily been
> made to work like 1.2 for users who were interested. After one moment
> of annoyance, I could have all of my sites functioning with Firebug
> with NO ACTION from me"
The Activate Same Domain solution in Firebug 1.5a7 may address this
point.
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
-~----------~----~----~----~------~----~------~--~---
