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

Separating the UI from the backend #16

Open
venkatd opened this issue Aug 16, 2023 · 1 comment
Open

Separating the UI from the backend #16

venkatd opened this issue Aug 16, 2023 · 1 comment

Comments

@venkatd
Copy link

venkatd commented Aug 16, 2023

Project looks very interesting!

Was thinking it might be simpler to focus on datacore being just the backend--indexing/querying capabilities--and have a "notion-like" view be a separate plugin.

You could first swap dataview to use datacore, then later focus on building richer UIs after that. That way the scope of datacore can stay manageable.

Thoughts?

@blacksmithgu
Copy link
Owner

This is a good design principle and for the most part the frontend and backend are wholly independent; that being said, the datacore query model is sufficiently different from dataview that the query language doesn't quite translate well.

I am currently trying to release a much more dataview-esque frontend to enable people to at least use datacore, while providing the nice performance and new query types.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants