1 / 4

Enhancing User Experience through Window and Tree Structure in Sudoku Samurai App

Explore optimizing Sudoku Samurai app by reorganizing windows and refining tree structure for better usability and efficiency. Discuss options like uniting windows and adding tree nodes effectively.

vanna-clayton
Télécharger la présentation

Enhancing User Experience through Window and Tree Structure in Sudoku Samurai App

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LEGUP HCI Aspects of the program structure Tyler “Sudoku Samurai” Hinman

  2. Window Arrangement • Original layout: Frames within one window • Now, each element (puzzle, tree, rules, menus) is in its own window • Taskbar clogging? • Make it possible to unite windows?

  3. Tree Structure • A user might click a node to bring back a previous state • If the user goes on to make edits, should those changes be reflected in the selected node, or a new branch? • Would it depend on whether things are being added or subtracted? • Should there be an Add Node button? • Should all nodes have to be added this way?

  4. Adding Tree Nodes • However we add nodes, when is it done? • Option #1: To add a node, the user must click Add Node, which will add a child to the currently selected node. The new node will inherit its parent’s state, ready to be changed. • Option #2: The user can select a node, make changes to it, and click Add Node, which will restore the existing node’s state at selection, then create the child reflecting the user’s changes. • Option #3: A new child is created automatically after any change, or perhaps a certain type of change (application of a rule from the menu, etc.)

More Related