You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that SvelteKit is 1.0 it can be used in production with Yark. I know SvelteKit and it seems like the best option for rewriting the viewer. I want to do this because flask templating can only really go so far, and having a nice fully-fledged viewer can have a lot of features added to it down the line.
The main reason I want to use SvelteKit for rewriting the viewer is that it can be made into a static JS-only page (as well as support in the future for more backends) which means end users won't need to install anything other than what they currently need to install to run Yark. Having Python 3.9 + FFmpeg is the maximum amount of fuss I ever want to subject users to, or ideally less than this if possible.
The following changes inside of the current project structure will happen:
viewer.py file will cease to exist and it'll be replaced by an api.py
This api.py file will be able to pull all data the viewer.py file can currently pull
Flask will be replaced by the fastest popular python api library there is
As much processing as possible will be handed over to SvelteKit
The following features could also be implemented once this issue is complete, but are speculative as of now:
Multi-archive management
Dashboard for complete GUI-based archive management, superseeding the CLI
I'm looking forward to the future of the project, but I'm not looking forward to programming all of this :)
The text was updated successfully, but these errors were encountered:
Now that SvelteKit is 1.0 it can be used in production with Yark. I know SvelteKit and it seems like the best option for rewriting the viewer. I want to do this because flask templating can only really go so far, and having a nice fully-fledged viewer can have a lot of features added to it down the line.
The main reason I want to use SvelteKit for rewriting the viewer is that it can be made into a static JS-only page (as well as support in the future for more backends) which means end users won't need to install anything other than what they currently need to install to run Yark. Having Python 3.9 + FFmpeg is the maximum amount of fuss I ever want to subject users to, or ideally less than this if possible.
The following changes inside of the current project structure will happen:
viewer.py
file will cease to exist and it'll be replaced by anapi.py
api.py
file will be able to pull all data theviewer.py
file can currently pullThe following features could also be implemented once this issue is complete, but are speculative as of now:
I'm looking forward to the future of the project, but I'm not looking forward to programming all of this :)
The text was updated successfully, but these errors were encountered: