API

Right now, Pastamancer and I agree that using a Roster library, or more precisely not using "unitid" as unit identifiers, was a mistake, and I'm working right now on a version of Grid that use "unitid" as unit identifiers. This will resolve a lot of problems with Grid when pets or units are sharing names now. This will also simplify a lot of code inside Grid.

Ace2 is obsolete, so updating to Ace3 is mandatory and we will be doing the update. I am not going to work (much) on UI or configuration, but Pastamancer seemed to have an interest here.

Finally, the interface between statuses and indicators needs to be reworked. But the details are fuzzy, at least for me, for now. Things to consider, apart from those already mentionned on this thread, are a tooltip indicator and a blinking state for indicators. Those two are often requested and the current architecture does not allow them.

Jerry is working on updating the current Grid codebase to use unitids instead of names internally and replacing the Ace2 dependancies with Ace3.

I'm currently working on a complete rewrite that will attempt to address most of the configuration woes. In Grid, I made the mistake of having statuses send information about how they wanted to be displayed (color, icon, bar value, etc.). This made a lot of things easier to code but has unfortunately made the configuration overly complicated and unintuitive. I also anticipated people would write replacements for the GridFrame module or even the GridLayout module, but that never happened. Turning the frame and layout modules into a core that you can plugin indicators and statuses will reflect current Grid usage and allow for a simpler configuration.

I want to have the configuration start with what the user sees, the Grid window. Users can then create and place indicators of any pre-defined type (statusbar, texture, colored-box, etc.) or any externally-supplied type (via a n additional module). Within each indicator, the user will be given a list of statuses. The statuses can be re-ordered in the list to determine display. Within each status, the will be able to determine how it is displayed on that indicator.

I want configurations to be easily shareable. I plan on having entire or partial configurations copy/pasteable so users can share them via forum posts and also shareable in-game via AceComm-3.0/AceSerializer-3.0.

Gamepedia

Tools

Content is available under CC BY-NC-SA 3.0 unless otherwise noted.Game content and materials are trademarks and copyrights of their respective publisher and its licensors. All rights reserved.
This site is a part of Wikia, Inc. and is not affiliated with the game publisher.