Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modularization #2

Open
8 of 27 tasks
QartemisT opened this issue Sep 4, 2021 · 1 comment
Open
8 of 27 tasks

Modularization #2

QartemisT opened this issue Sep 4, 2021 · 1 comment
Assignees
Labels
🛠 Enhancement New feature or request Low Priority This issue will not be worked on unless there are no high or medium tasks left

Comments

@QartemisT
Copy link
Member

QartemisT commented Sep 4, 2021

Stuff that could/should be modularized;

  • DBM Scheduler
  • Dev Tools
  • Icons
  • Target Scanning
  • Options/Default options
  • Util functions
  • Sync code
  • Event registering
  • Mod creation
  • Addon load handling/Load boss mods on demand
  • Profiles
  • Commands
  • Hyperlinks
  • Raid party handling
  • Update reminder
  • Notes editor
  • Pull/Kill/wipe detection
  • Auto respond/status whisper
  • General methods
  • Class methods
  • Boss Health functions
  • Announce objects
  • Yell Objects
  • Special Warning Objects
  • Timer/Beserk/Combat Objects
  • Timer/Variable recovery
  • Localization
@MysticalOS
Copy link
Member

MysticalOS commented Sep 4, 2021

i feel like that's too many modules. some stuff does go together.

For example, pull and kill/wipe should be together. It's all intertied anyways with incrimenting or deincrimenting counts. they share tables such as the difficulty conversion table which you'd have to duplicate otherwise.

timer and berserk/combat objects should be together.

many core routines should probably be together such loading on demand, options and default options, profiles (since these are all intertwined with loading). Maybe "Initilization" module.

Util and general methods should probably be together.

@MysticalOS MysticalOS added Medium Priority This issue doesn't make DBM unusable, but makes it less useful until complete 🛠 Enhancement New feature or request labels Sep 19, 2021
@MysticalOS MysticalOS added Low Priority This issue will not be worked on unless there are no high or medium tasks left and removed Medium Priority This issue doesn't make DBM unusable, but makes it less useful until complete labels Oct 13, 2021
@QartemisT QartemisT pinned this issue Nov 22, 2021
@MysticalOS MysticalOS unpinned this issue Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🛠 Enhancement New feature or request Low Priority This issue will not be worked on unless there are no high or medium tasks left
Projects
None yet
Development

No branches or pull requests

2 participants