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

Edit Mode for WeakAuras #5041

Open
emptyrivers opened this issue May 1, 2024 · 3 comments
Open

Edit Mode for WeakAuras #5041

emptyrivers opened this issue May 1, 2024 · 3 comments
Labels
🎨 Feature Request This is a request for a new feature, or an expansion of an existing feature.

Comments

@emptyrivers
Copy link
Contributor

emptyrivers commented May 1, 2024

I've had this idea percolating in my head for a while. Probably past time to put it on paper where others can see it.

This is IMO very intuitive & easy to use. Easily one of the best UI innovations from blizzard. Some of the ideas are already in use (e.g. the grid snapping is very similar to our "Magnetically Align" toggle). We should crib more of the ideas in here.

image

There's this library, it might be worth looking into for aiding implementation.

I'm imagining this especially, as a kind of supercharged Hybrid Sort on dynamic groups:

  • user can create Anchors A, B, C, etc. Child Auras can be plonked into anchors arbitrarily. There's a hint of that idea in groups 2: dynamic boogaloo #3094, actually - custom distribute code can place children on multiple distinct anchor points.
  • These anchors can be moved around visually on the screen, in the same way that Edit Mode Works. They can glom onto each other, or onto other groups or grid lines, or theoretically anything else in that edit mode. We could crib much of the logic that Edit Mode uses to cleanly resolve the anchor chain (to the user, it "just works" which I find very impressive).
  • Anchor A could display auras in a line. Anchor B might display auras up to $MAX total auras, while the remaining 'cascade' into B_2, which displays also auras in a line, but offest & scaled down compared to Anchor B. Anchor C might clone itself onto nameplates, and distribute its children amongst the clones of itself (this is also an idea cribbed from groups 2: dynamic boogaloo #3094).
@emptyrivers emptyrivers added the 🎨 Feature Request This is a request for a new feature, or an expansion of an existing feature. label May 1, 2024
@github-actions github-actions bot added the ⏱ Awaiting Response This ticket hasn't been triaged yet. label May 1, 2024
@emptyrivers emptyrivers removed the ⏱ Awaiting Response This ticket hasn't been triaged yet. label May 1, 2024
@Jodsderechte
Copy link
Contributor

This would actually be a great Edition and solle the same issues naemesis and reloe have been trying to solle with their anchor auras. One thing that would be useful would be reusing auras automagically. What I mean with that is prob the most Common auratypes are class auras and bossmod type auras. Two possible solutions i can think of right now:
1: There could be some default anchor of those Popular types that authors could reuse

2: Authors could export anchor definitions with their aura packs that could then be reused by authors talking about a standard. This is prob best explained on an example: Causes creates raidpack 1 that has anchor definition warning, highlight and emphasized. These anchors get created on import(if they dont exist already) or just use the present ones. Then for raid 2 I decide to use relios pack that defines anchors warning and cool down. The warning would immediately be matched while cool down anchor would need to be created. Unsure if this should be by name or Id or something.

@mrbuds
Copy link
Contributor

mrbuds commented May 1, 2024

Something to consider is that Edit Mode doesn't exist on Classic SOD & Classic Cataclysm

@emptyrivers
Copy link
Contributor Author

well then classic can just slum it with AceConfigDialog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎨 Feature Request This is a request for a new feature, or an expansion of an existing feature.
Projects
None yet
Development

No branches or pull requests

3 participants