Open icykoneko opened 4 years ago
icykoneko
commented
4 years ago Talked to owner of xivapi. If we do switch to this, I would still want to continue building the giant image sprite to speed up the UI.
I think this feature can be done in stages, basically replace parts of the backend python scripts to use xivapi as the data source, instead of Saint Coinach. Once all of that's working, I'll make a separate issue for building the site completely online.
Simbiat
commented
2 years ago Are you sure that simply using lazy loading would not provide better results in performance, though? Considering the images are small and you do not show them all at once, the size would still be lower than the size of the whole sprite on initial page load. Latency caused by actual connection for each image may provide some delay, but even if it will be noticeable, you can mitigate that by using HTTP2 push. Although that would require knowing what exact images are meant to be shown on page load.
Currently, the backend is built using my own python port of Saint Coinach. That part is fine, but it does require you to actually have a copy of the game installed.
There's benefits to the existing system though. When a new patch drops, assuming not much changed in the data layout, it's possible for me to immediately load up new fish into the YAML. I don't know the turnaround time for xivapi's site.
On the other hand, by using xivapi instead, it should be possible to completely build and deploy the site all online.