Comment # 4
on bug 11975
from Guy Harris
(In reply to Henry Stukenborg from comment #3)
> The problem with multiple floating windows is one of scalability; if you
> start opening individual frames or other dialogs and they're all floating
> free in separate windows, the UI quickly becomes a rats nest; actually, if
> you open multiple WS processes and open packets for each, you wind up with
> the same rodent problem.
And the problem with tabs within a single window is that you can only look at
one of the items within the tabbed window at the same time; you can't look at
both {browser windows, terminal windows, PDF documents (I'm looking at *you*,
old version of Acrobat for Unix - that was *horrible*), captures, etc.} at the
same time.
Yes, given that I have close to 100 Safari windows open, I'm aware of the
issues with multiple floating windows - but having them all as separate tabs
just gives you a different flavor of rats nest.
> Perhaps the goal is to solve the more pressing issue of trace comparison,
> which is really what I'm driving at. For example, if I do a wireless capture
> and have the analogous wired-side and client-side traces, I'd like to be
> able to align and compare them, but currently that requires a lot of screen
> real estate, patience and ungodly amounts of caffeine.
And how does stuffing the two traces in a single window make that *not* require
that?
You are receiving this mail because:
- You are watching all bug changes.
