brndmfrd / pfcharactersheet Goto Github PK

Keep track of edits when there are unsaved changes.
Read from config file how often to periodically save the active character.

Shared resources from the ActiveCharacter project, and all shared resources, should be placed in /Shared.

Data access layer is insufficient to meet the needs of the application.
A new DAL is needed to properly model the active character data for
use in the application.

Option to save when closing.

A save button on active character views enabled when a new edit is made.

Service to serialize and save file from active character.

Add the option save the current active character before loading new character data.

StartupScreenModule.Models.LoadCharacter.BeginLoadCharacterFile() should load and de-serialize a character file similar to how it was saved. This method needs to ensure a lock is made on the target file and ensure correct loading of data in the Active Character class.

Separate the ability scores from the rest of the character info for easier viewing (New region on right side of 'Character' page).

A configuration file. Contains default character file save location and auto-save duration.

Take a look at the ActiveCharacter > Sharedresources > NavigationStyles[NavigationButtonStyle].
We can likely add more to the style and reduce the fat from the rest of the style construction on the rest of the buttons. For instance, labels are used for custom text on buttons. Try customizing the font on the buttons and using the buttons native Content="" parameter for button text.

The primary and aux content should be framed as it is in the character creator.

Add selection options for character class and race.

Add the option for uses to use a smaller, scaled version of the GUI.
Add the option for users to change the color, font, and add custom skins to the background and various regions of the UI.

The controls should be accessed through the nav bar > options > config

Add item macro buttons to character creation to allow players to add common items to the character creation view.

The directory /Shared contains a class library of classes to be shared throughout the solution. It is currently named "ModuleTools" and should be changed to "SolutionTools" or something more fitting.

Add empty space buffer for scroll menus.
Or scrollbar. Or arrow.

The format of character sheet files (.pf) needs to be defined.
I was thinking .json for obvious reasons.
This being said should we divide up the .json based on the tabs of the program?

I feel like the Character.cs needs to be reworked. I'm not sure how, exactly.

Add service to load character from file to active character.

Add edit options to each character view.

Add save button to Nav bar (Nav bar).

Make the currently selected tab highlighted.

Add command line interface/message box at bottom center (all pages).

Add current effects (rectangular region, all screens, top center.)

With all the changes Unit tests have been obliterated. They need some attention to get back up to their former glory.

Find a color scheme that is easier on the eyes for file mgmt (save/load).

Add as many default values for character data entry fields as reasonable. Also add some default blank entries to the character creation views; for example, all new characters should have an entry for the character name, the player name, character age, etc.

Add the ability to load the newly created character into the active character values.

Excess references are all over the code. They need to be removed safely.

A better naming convention for the resource dictionaries. Move them to /Shared.

Add an edit button in character view so user can change loaded values (character).

References across the board needs to be cleaned up.
Remove all superfluous references and uses.

A way to create new characters needs to get developed. Right now we can only save and load.

Change startup page ("Create/Load") page to "Options."

1. Keep 'Create new character.'
2. Keep 'Load character.'
3. Add 'save' option.
4. Add 'config' settings.
   * UI size (sm, med, lg)
   * Colors & skins

Ensure all values on a character sheet are represented somewhere in the app.

A list of considerations. What can be equipped and where. Wealth and movement. Rolls. Hit Points. Temporary Hit Points.