[TODO] Deck Handling System

[KOOKIIEStudios]

Abstract

We intend to use a deck handler that comprises 3 sub-systems working in tandem. This issue thread serves as the parent thread; there will be issues for each subsystem linked under the task section, which in turn have planning-related issues linked inside them.

Details

• Deck Manager
  • Allows traversal between these two UX systems, through a GUI interface
  • Displays a list of saved decks and an option to create a new one
  • Right clicking on existing decks opens a context menu with the options to view or modify
  • Left clicking on existing decks opens them up in the Deck Viewer
  • [OPTIONAL]: Display description field on mouseover
  • [OPTIONAL]: Tag/label filters
  • [OPTIONAL]: Sort functionality
• Deck Viewing system
  • Displays the contents of a selected deck
  • Export function, that spits out deck list string
    • [OPTIONAL]: Automatically save to users' clipboard
  • Option to modify the deck that is being displayed (sends user to Deck Builder)
• Deck Building system
  • Assigning cards to a new deck
  • Modifying existing decks
  • Sends user to Deck Manager upon save/exit
  • Import function, that takes in deck list string
  • [OPTIONAL]: Additional attribute fields
• Server-sided utils
  • Parser for deck list strings (offloaded from client to server)

Tasks

• Deck Manager: [TODO] Deck Manager #59
• Deck Viewer: [TODO] Deck Viewer #58
• Deck Builder: [TODO] Deck Builder #4
• Implement deck list parser
• Set up socket.io emits to handle the parsing