Separating the UI from the backend
venkatd opened this issue · comments
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?
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.