P/dropbox

[Silverfeelin]

Adds the option to connect to Dropbox and use it for data storage. Storage is limited to:

• unlocks (items, nodes, IAPs).
• winged light (children of light; wing buffs are 'items' so those are in unlocks).
• favourites.

This code is experimental and is available for preview at: https://p-dropbox.sky-planner.pages.dev/

Overview of changes:

For local storage, any steps that involve loading or saving will be (near) instant.

• Route tree changed to allow loading data and storage before navigating to the pages that require this data.
• When navigating to pages that require storage data, loader will be shown (first page only).
• New pages added to manage storage options, connect to Dropbox and show if (somehow) loading the item data failed.
• Menu has been moved to the route tree so routing to and from pages like outfit request no longer require a refresh to determine visibility on page load.
• Added the IStorageProvider interface that allows integrations for different cloud services in the future.
• Moved localStorage event emitter from StorageService to EventService so it's not bundled with the code that saves to cloud instead of localStorage.
• Data loss warning moved from localStorage listener to BroadcastChannel so tabs can be notified regardless of storage provider.
• Save icon is shown when data is not saved yet, saving, save failed and when saved. Icon will disappear on successful save after a few seconds.
• When loading from the provider fails, redirects to the storage page with the error message.
• When saving to the provider fails, shows the error message in an overlay with an option to retry or return to the storage page.
• Stored data (i.e. unlocked items) is now applied to the Sky data when both the data and storage load instead of directly when the data loads.
• Moved blur filter from sky-card to sky-card-header and sky-card-footer so it doesn't blur the section below the visible card in flex/grid.

Todo:

• [x] Title resolvers no longer function because they resolve before the data is loaded. Generic titles are currently shown (for example Season instead of Season of xyz).
• [x] When items are unlocked in the source data (i.e. default hairs), these are no longer added directly to the unlocks.
• [x] Reintroduce import / export. The export can be reused from old code. The import can make the changes through the storage service which will use the current storage provider to save them.
• [x] Mechanism to check if current page data is out of date (when a newer file is in cloud storage).
• [x] Sky clock is incorrect (matches local time).

Closes #60 Closes #87

[cloudflare-pages[bot]]

Deploying sky-planner with    Cloudflare Pages

Latest commit:	a562687
Status:	✅  Deploy successful!
Preview URL:	https://96f465d0.sky-planner.pages.dev
Branch Preview URL:	https://p-dropbox.sky-planner.pages.dev

View logs

[imnaiyar]

Okay, so I tried this, and so far, I don’t see any issues with it. I think this is a viable option for saving data long-term. Also, I noticed you added many useful things. Kudos to you! Also, I was wondering if you plan to make it an installable app (on supported devices).

[Silverfeelin]

@imnaiyar Thanks for the update. I will still go around testing the site for a bit longer since a lot of changes were made to the code. Once this feature is released you can connect to the same Dropbox account and it'll work with any data you've saved on the preview site.

Right now I have zero plans for making an app. Even with these cloud storage options, the website data (items, spirits, etc) are static to keep it easy and free to host the site. Publishing an app for Android/iOS would, next to its own challenges, require me to maintain multiple versions of this project and add a server so I don't have to go through the app approval process every time I add new Sky data like event items.

I'm pretty sure even with the current site traffic it's already beyond what the free tiers of several options like Cloudflare support. Plus it's not scalable so I'd be reliant on donations or ad revenue to keep the site running. The current format just makes a lot more sense to me.

I do try to keep everything responsive so the website can be used on desktop and mobile and welcome any suggestions to make it easier to use on mobile (in new issues).

[imnaiyar]

Oh, sorry if I was confusing, I meant PWAs Installable web app (For supported Browsers). If that's something you'd be willing to add (I don't think it would take much effort, a manifest file, and a service worker). But I'd understand if you don't want to

[Silverfeelin]

I'll have a look at it some time in #91. I don't know much about PWA. If it's something I can include without changing the project too much then it could be an interesting project after cloud storage.