-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add web support #70
Add web support #70
Conversation
939089a
to
5b82a47
Compare
5b82a47
to
0e29b66
Compare
I think it's fine to have it, but since Vikunja already has a great web frontend with a lot more features, I don't really see a reason to add (and then maintain) this. |
For me the biggest advantage is to be able to develop the features locally with Chrome (or Chromium). We can maybe keep this target enabled but without officially supporting it |
Edit: nevermind, I just realized you probably mean the features for the flutter app. You're obviously right, we can definitely keep it in for that! |
Similar to what Beni said, we won't use the flutter web app as a replacement for the current web frontend anytime soon. I think having an easy way to develop for it without requiring a full-blown Android dev environment is a very good thing. Can you add a note to the readme about how to get started with flutter web and how we'll only use it for development? |
The Readme is on my todo list anyways, so I'ma just add this when I update it! |
Depends on #69 (stacked PR, the diff is going to be huge until #69 is merged, just review 5b82a47)
This PR adds support for the
web
platform to make it easier to develop the app further. Eventually, this could be a second frontend to Vikunja - although this is not really the reason why I'm doing this.With this PR, I've also fixed an issue that was seen during Hot Reload in the web, where the theme was not correctly reset.