mcnerdius / doom Goto Github PK

• 5.5
• 5.4
• 5.3a
• 5.2
• 5.0
• 4.5a
• 4.0
• 3.8
• 3.7

Note: Dumps will be versioned, as follows:

CorruptionCards-v#.#?-yyMMdd[.embedded].json

When creating a dump via CLI:

• If new dumpfile is identical, retain old and delete new
• If new dumpfile has changed, move prior to /old

When compiling Core:

• Exclude /old

• Monster Groups
• [ ]

Current view is a <lit-virtualizer> scroller full of <card-view> components showing all of the card's info. Lots of scrolling, more geared toward deck customization. Add a grid view similar to the Card Compendium.

• Add a dense or similar attribute on <card-view> to display image and name only, maybe hint. Or hint as tooltip ? Or something else as tooltip ?
• import {grid} from '@lit-labs/virtualizer/layouts/grid.js'; / .layout=${grid()}
• Clicking a card in grid view pops up the full List view equivalent
• Grid as default; User has toggle option; Switching to Customize toggles to List automatically.

Version, Deck, Tier, Type and possibly other very basic things always visible and compact.

The rest will inevitably take up more space and thus should be hidden by default and designed with responsiveness in mind. The number of entries per group could be 10-15+ (todo: get the data), all items in a group should be on screen.

• Stacking the Advanced filter groups between the Basic filters and the Cards view:

  • Noisy, pushes Cards view down.
    • Put filters on bottom ?
  • Single-line + scroll large groups, or stack ?
  • Less screen space, same layout on mobile & desktop

• Placing them to the side:

  • Takes up more screen space
  • Would need to switch to above layout for mobile

• CardTag: add icon to UI
• Generic card: Create a simple component to fade between monster graphics to represent this. Being faithful to custom Monster Groups will need to happen down the road when loading custom decks happens.
• Custom Frame
• [ ]

This will supplement/complement Filtering.

GetCards API:

• Takes an optional CardFilter.cs which is essentially a mirror of Card and implements IEquatable<Card>. Its props are all nullable, and unifies common string props as .Text.
• Returns Dump.Where(CardFilter), a simple Card[]

Filter UI:

• Consumes the Card[]
  BUT ALSO:
• Collates the filtered matches by property & value to provide match count data to display.

Collating this data is somewhat expensive. This will still be a two-step process done server-side, but doing so:

• Eliminates redundant CardFilter.ts and "clever" lifecycle & template logic
• Allows for a direct mapping of API data to template.
• Resembles future graphQL work.