Summary: | Adding drag/drop support to TreeOutline | ||
---|---|---|---|
Product: | WebKit | Reporter: | Patrick Mueller <pmuellr> |
Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Enhancement | CC: | aroben, burg, joepeck, kmccullough |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | All | ||
OS: | All |
Description
Patrick Mueller
2009-10-08 11:42:49 PDT
I'm not 100% if these are all tree outlines. Elements Tree Hierarchy: - Reordering / Moving Nodes - Holding down the option (⌥) and dragging could clone a Node. Elements Sidebar Panes: - Reorder Panels and Store in a Preference to Customize the UI a little EventListeners Sidebar Pane: - Reorder Listeners in the Event Flow - Drag a Listener onto an Element in the Tree Hierarchy to copy the listener to that node. Elements Tree Hierarchy (addition to items above) - gesture to delete a node by dragging it offscreen - actually not sure we can do that, maybe we need a valid drop target? hmmm ... a trashcan? - Breakpoints - move, delete, copy - formatted 'text' like Elements Tree Hierarchy, JavaScript Source, Console; should be able to drag out to a text editor - supporting formatted (html) and plain text - number-y things like resource graphs, profiler tables - drag out as plain text, html, and csv. - drag Call Stack as plain text or html <ol>, probably want to also include Scope Variables there as well. - various tables in Storage pane - export as plain text, html, csv The previous note on using option (⌥) dragging seems to imply we should have some app-wide modifier keys / extended action definitions. ctrl- means copy, shirt- means something else, etc. - Drag a CSS Selector of a classname onto a node to apply that class to that node: https://bugs.webkit.org/show_bug.cgi?id=16529#c2 TreeOutline (at least for the DOM tree) is draggable. We need to file smaller separate bugs for specific DND interactions. |