The Vikunja app relies on the backend a lot. Most of the API interactions are in the src/services folder. So what I’m doing is rewriting the services to use a “local backend” (src/localBackend folder). For now only tasks are somewhat implemented. The webxdc API is not used at all, so no cooperation for now.
My plan is:
Improve typing of services to better see where they are used in the app
Implement the most important services locally (tasks, kanban buckets)
Use webxdc API (set up sync between users)
Simply remove the code that relies on unimplemented services
Maybe implement some more of the services and bring back the features that rely on them (lists, namespaces, users).
See the result and evaluate whether it’s sensible to try to integrate the changes into the upstream (the maintainers said that it’s unlikely). The alternative is to keep a separate git branch and keep merging the upstream into it (resolving conflicts could be a pain).
If you have ideas for improving the steps, please share.
Ok, looks like there is actually a lot of logic that is backend-only. See, for example, the (t *Task) Update function. Marking a task as “done” is not just a matter of flipping its done property. See the updateDone function. There’s plenty of stuff going on. If you send done: true to the backend it could flip it back, depending on, for example, the repeat_after property.
I’m afraid that simply translating the Go backend to JS is not the way to go.
Strip off some of the functions, like repeating tasks.
Actually try to make a best-effort Go-to-JS translation, with no guarantees that it’s gonna behave exactly the same as the original one.
Try to modify the upstream repos, transfer as much logic as we can to the front-end, i.e. make it so that the front-end doesn’t try to set done: true if the backend would actually flip it back to false.
It seems kind of weird that if you send done: true it returns done: false anyway. But maybe it’s because the alternative is to make a properly named and described endpoint, while keeping the logic the same.
Somehow use the actual Go backend. Translate it to WASM + JS with Emscripten? That would make the bundle super big. And can you translate the database that the backend uses as well?
is implemented, it’s gonna be much easier to convert it to fully offline. But they say it’s complex, so not sure if/when to expect that.
I’m still working on the fork though, will probably post another version soon.
It still pretty raw and doesn’t have any sync between users, and you can’t use it on the device that you sent it from due to .xdc file size limitations in Delta Chat (ask the chat members to forward your message to the same chat, and it will work for you).