richteer / gw2at Goto Github PK

The data we store in local storage currently mirrors exactly how the application uses the data, however that may not be the case if we end up changing how the data is used internally. In other words, we should label the more involved data objects with a version, so if the application updates and you refresh the page, it can still reload old data.

Not everything needs to be versioned, unless we move to a model where the whole state object is preserved (which may not be an entirely terrible idea, to reduce the number of keys we have to store). Most notably though, the list of tabs and their contained data should be versioned, so in the event we change the format, we can forward convert an old version to the new version. Ideally, we should implement and deploy this before we actually intend to increment the format version.

Some achievements (particularly the Glory achievements) have quite a few tiers, and can get noisy when the browser isn't particularly wide. There should be an option to hide completed ones, and maybe show only the next one. Maybe have them appear on mouseover if possible?

Stuff 'n such

Example: the current dragon bash festival achievements and feats do not show up in the tracker, since there is no "festivals" group returned by the achievements/groups endpoint. However, they can still be found in the achievements/categories endpoint. This is presumably also true for some achievements that may not be pointed to by a category.

Unfortunately, due to the crappy shortsighted upstream API design, this means we can't rely on dynamically requesting group/category/achievement data each time the page is loaded -- it might be better to pre-process the data to fill in this missing gaps in the API

Create a proper dark theme. Inverting the color scheme of everything is not the best solution.

At the risk of making it a bit noisy, the achievement selector should probably show more at-a-glance information (possibly configurable).

At a minimum this should include:

• Locked status, for achievements you can't currently make progress towards
• Hidden achievements, since these won't show up in the game UI
• Achievement with AP available, for those AP hunters
• Achievements already being tracked (possibly show which tab(s) in tooltip)

Maybe also consider:

• Percentage complete, for at-a-glance selecting of close-to-completion achievements

Reserving issue #1 to track the features needed to consider this "pretty much done" and usable by others.

Be able to select daily categories (festival, fractal, strike mission, etc) to track on a special tab.

Achievements should sort when updated, for example, the most completed achievement (by %) should always be listed at the top.

Achievement selector currently requires you to refresh the page to request new data from the API. This mostly affects dailies, as it will work with cached data.

The achievement selector currently doesn't really work well with updating data, so it will need some re-mangling probably.

We should consider moving all caching into the GW2API class, and have the achievement selector always "request" the data each time, and then have the GW2API class determine if it should respond with the cache data, or actually retrieve new data.