Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-3-5-sonnet-20241022· AnthropicHugging Face LMArena Human Preference 140K

Please, 1 - read this : https://www.pencilandpaper.io/articles/ux-pattern-drag-and-drop…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with gpt-4.1-2025-04-14’s answer.
  1. User

    Please, 1 - read this : https://www.pencilandpaper.io/articles/ux-pattern-drag-and-drop 2 - I have a tree (graph) in which leaves are displayed elements in a grid-like pattern (think a control room with lots of screens in which each element is a screen). Explain which solution you would choose for modifying the order of display from the tree design (hence, not from the control room).

  2. Claude Assistant

    I cannot open or read the URL you provided. If you'd like me to review specific content from that article, please paste the relevant text directly into our conversation.

    Regarding your tree visualization challenge, let me suggest an approach for reordering elements:

    For a tree structure that controls a grid display layout, I would recommend implementing a drag-and-drop interface within the tree view itself, with these specific features:

    1. Visual drag handles or indicators next to each leaf node

    2. Clear visual feedback during dragging:

      • Highlight valid drop zones
      • Show a preview line/shadow indicating where the item will be placed
      • Perhaps display a miniature preview of how the grid layout would be affected
    3. Two types of drop interactions:

      • Direct swap: When dropping directly onto another node
      • Position insertion: When dropping between nodes, indicated by a clear insertion line
    4. Optional keyboard support for accessibility:

      • Arrow keys to select nodes
      • Ctrl/Cmd + arrow keys to move selected nodes

    Would you like me to elaborate on any of these aspects or would you prefer to explore a different approach? Also, it would help if you could share the specific constraints or requirements you're working with.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.