On Jul 6, 10:13 am, nod <[email protected]> wrote:
> Okay, let's start fresh and try this again. Long time user, 2nd post.
And now I am trying a second reply...
>
> Looking through the newsgroup, I see several people trying to
> articulate this point and explain why it's such a significant problem,
> without success on the receiving end. I don't know if I'll be more
> successful, but I'll be trying to be very concrete, logical, and step-
> by-step.
>
> Core problem description: conflation of UI visibility with activation
> I'll be trying to explain:
> 1. what this is
> 2. that this is different from previous Firebugs
> 3. why the conflation is a bad thing
> 4. why the way the change was implemented is a bad thing
>
> Scenario A:
> 1. Ctrl-F12, "Open Firebug in New Window"
> 2. See a greyed-out window with a button in the middle saying
> "Activate Firebug for the selected Firefox tab"
> 3. Think "ok, I will activate Firebug so that it will be 'on' and I
> can debug this web page"
> 4. Click the Activate button.
> 5. Discover that a page refresh is needed, and refresh the web page.
> 6. Use Firebug to investigate an issue in the web page
> 7. Be finished with Firebug for the moment, but want to continue
> working with the web page
> 8. Use i) Ctrl-W, ii) File->Close, iii) the red "X", or iv) "Open
> Firebug in New Window" to close the Firebug window.
> 9. User now thinks Firebug window is closed, but that Firebug is still
> running (like all previous versions) on this web page.
So the question I ask you is: what do you want 1.4 to do at this
point?
You want the page to remain active. But you don't want Firebug to be
detached.
In 1.3 Firebug acts as if you minimized. I think we can do that again.
The hard part here is insuring that the information stored in the
external window is again synced up with the information in the browser
window. The code that did this in 1.3 was bizarre, no one understood
it.
...
> Here are a few more problems with external window mode that are
> inconsistencies with even the new conflated model: (These are NOT the
> main issue here, they serve just to further illustrate how the
> semantics of UI visibility are subtly different for in-page mode and
> external window mode, further illustrating how the central conflation
> fails to work usefully and understandably.)
...
The other message I want to get out about open in new window is
simple: we don't have the development resources to handle all of the
Firebug code. One option I have considered is dropping the external
window feature. Not dropping it is a decision which causes other work
to be dropped. So I urge folks who want the external window feature
to be supported: use the alpha and beta versions and give feedback
during the development. Since we don't here from you, the feature does
not get the attention you think it needs.
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
-~----------~----~----~----~------~----~------~--~---
