Canmove, confirm, emeritus
1,093
edits
Changes
no edit summary
# what is the scope of panels and how does it change as you move between tabs?
# how can panels that are frequently used together be denoted as such?
# how do we handle “activationâ€"activation"? (Which sites the tools show up for automatically? which tools? how are they grouped? how do we keep expensive tools from slowing things down?)
= Panels =
== Docked Panels, side-by-side ==
[[Image:DevTools/Features/UI_docked_side_by_side.png|Two panels docked side-by-side]]
== Floating Panels ==
[[Image:DevTools/Features/UI_docked_and_floating.png|One docked and one floating panel]]
== Floating Tool Window ==
[[Image:DevTools/Features/Tools_floating.png|Two panels docked in a separate window]]
= Scope =
Each tool works in a particular “scopeâ€"scope". For most users most of the time, the scope is simple and invisible: the tools are tied to the tab for which they were created. Tools ''can'' be given a new scope along the way (see below).
If the user switches tabs, any tool windows or floating panels will disappear (and any tools that were in use for the new tab will be displayed).
= Gauges =
Another idea: add-ons could provide “gauges†"gauges" which would generally be viewed together in a strip. Memory, CPU usage, network traffic, framerate. Anything that can be displayed in compact way.
= Alert Mechanism =
All installed tools should be able to alert the user, regardless of which tools are open. Note that this gets into the “activation problem†"activation problem" that Firebug has solved.
Alerts to consider:
