Skip to content

Feature: Inheritance Second Gen#5

Merged
kronikarz merged 1 commit intodevfrom
ow-feature/inheritance-second-gen
Dec 21, 2024
Merged

Feature: Inheritance Second Gen#5
kronikarz merged 1 commit intodevfrom
ow-feature/inheritance-second-gen

Conversation

@balladyna
Copy link
Collaborator

This feature introduces genealogical tree view to display monster generations, allowing users to visualize lineage dynamically. It includes widgets for first and second generations, where users can generate and customize monsters by adding IV values, changing colors, and resetting defaults via interactive sliding panels. Additionally, it manages the state and functionality of IV buttons for the first and second indexes of the first generation, ensuring seamless interaction and logical consistency for these elements.

List of changes:

  • created genealogical_tree_page to display monster generations
  • created monster_model to define monster attributes: IV colors, auto-fill status, generation name, and methods for adding/resetting values
  • created first_gen_widget: which dynamically generates 2–32 buttons based on user input
  • created first_gen_sliding_panel: with buttons to add IVs, change monster colors, and reset values
  • created first_gen_cubit: for state management (ivColor changes, enabling/disabling buttons, restoring defaults) of first gen
  • created first_gen_model: to manage business logic: adding IVs, resetting values, and performing index calculations
  • created second_gen_widget: which dynamically generates up to 16 buttons based on the first generation number, auto-filling values if parent values are set, and resetting when a parent is restored to default
  • created second_gen_cubit for state management (inherit IV values from previous generation and ivColor changes)
  • created second_gen_model which similar to firstGen, managing business logic: adding IVs, resetting values, and performing index calculations
  • UI improvements: blocking display of widgets off-screen and enabling navigating to the previous view using system button

This feature introduces genealogical tree view to display monster generations, allowing users to visualize lineage dynamically. It includes widgets for first and second generations, where users can generate and customize monsters by adding IV values, changing colors, and resetting defaults via interactive sliding panels. Additionally, it manages the state and functionality of IV buttons for the first and second indexes of the first generation, ensuring seamless interaction and logical consistency for these elements.

List of changes:
- created genealogical_tree_page to display monster generations
- created monster_model to define monster attributes: IV colors, auto-fill status, generation name, and methods for adding/resetting values
- created first_gen_widget: which dynamically generates 2–32 buttons based on user input
- created first_gen_sliding_panel: with buttons to add IVs, change monster colors, and reset values
- created first_gen_cubit: for state management (ivColor changes, enabling/disabling buttons, restoring defaults) of first gen
- created first_gen_model: to manage business logic: adding IVs, resetting values, and performing index calculations
- created second_gen_widget: which dynamically generates up to 16 buttons based on the first generation number, auto-filling values if parent values are set, and resetting when a parent is restored to default
- created second_gen_cubit for state management (inherit IV values from previous generation and ivColor changes)
- created second_gen_model which similar to firstGen, managing business logic: adding IVs, resetting values, and performing index calculations
- UI improvements: blocking display of widgets off-screen and enabling navigating to the previous view using system button
@balladyna balladyna requested a review from kronikarz December 21, 2024 20:36
@kronikarz kronikarz merged commit 6940d2f into dev Dec 21, 2024
2 checks passed
@kronikarz kronikarz deleted the ow-feature/inheritance-second-gen branch December 21, 2024 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants