[Webkit-unassigned] [Bug 45657] Web Inspector: [Resources panel]=?UTF-8?Q?=20Need=20more=20visible=20=E2=80=9Cat=20a=20glance=E2=80=9D?=.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=45657





--- Comment #4 from Pavel Feldman <pfeldman at chromium.org>  2010-09-15 23:05:06 PST ---
So I thought about it a bit and here is what I think:

1. We do mix the "network log" aspect with the "resource browsing" aspect in inspector.
2. Firebug's looks is much more favorable for the network-related use cases (IE9 adopted it too btw)
3. We can't migrate to FB's way since we'd like to navigate to resources from various places (such as CSS rules)

Here is a rather provocative and high level suggestion. I did not think for too long, just throwing it at you.
1. Rename "Resources" tab to "Network" tab and mimic Firebug's way there. Everything, including expandable rows and content preview. It is now a 'network log', not a 'browser'
2. Merge existing Resources tab into the Storage tab. Add a 'NETWORK' group there that would host all of the resources. These resources will have Headers, Contents tabs when you select them.
3. Replace Storage groups with the tree view to make it more lightweight

Rationale:
1. We separate "network log" and "resource browsing"
2. We cover both aspects, do not introduce new panels
3. We can add further IDE aspects to this new "Resources" tab.
* We get little things like when resource is loaded off the appcache, we show it under the appcache node, not under the network.
* Need to think about the Resource vs Scripts panel more. Maybe Scripts panel should instead be Resource panel's perspective (Eclipse terms) that arranges the screen for more convenient debugging. That is internal design though.

Timothy, what do you think?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.