Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Viewer rewrite with SvelteKit #86

Closed
Owez opened this issue Jan 15, 2023 · 2 comments
Closed

Viewer rewrite with SvelteKit #86

Owez opened this issue Jan 15, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@Owez
Copy link
Owner

Owez commented Jan 15, 2023

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 :)

@Owez Owez added the enhancement New feature or request label Jan 15, 2023
@Owez Owez self-assigned this Jan 15, 2023
@Owez Owez added this to Yark 1.4 Jan 15, 2023
@Owez Owez moved this to Todo in Yark 1.4 Jan 15, 2023
@Owez Owez added the future Backburner issue which is for versions in the future label Jan 18, 2023
@Owez Owez removed the future Backburner issue which is for versions in the future label Jan 27, 2023
@Owez Owez removed this from Yark 1.4 Jan 27, 2023
@Owez Owez added this to Yark 1.3 Jan 27, 2023
@Owez
Copy link
Owner Author

Owez commented Jan 27, 2023

Doing this in 1.3 because this makes Yark so much cooler

image

@Owez Owez mentioned this issue Jan 27, 2023
@Owez Owez moved this to In Progress in Yark 1.3 Jan 29, 2023
@Owez
Copy link
Owner Author

Owez commented Jul 7, 2023

Closed in favour of a Blazor rewrite in the ongoing #105 :)

@Owez Owez closed this as completed Jul 7, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in Yark 1.3 Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant