You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
evolve from pure dataset visualization to being a frontend framework for data portals (i.e. "presenting" datasets either individually or a full catalog)
Why
Recline is (definitely) showing its age and is need of an upgrade. A lot of this work has been done (e.g. at Datopian) and we can now merge this in.
Recline was created in 2012-2014 as a library "for building data applications in pure Javascript and HTML". Its main use (and purpose of development) was use in CKAN. It has been great there but it's showing its age.
A lot of development has taken place in ecosystem since then that we can take advantage of e.g. React, Vue, lots of new charting libraries etc.
A lot of development done at Datopian to update Recline e.g.
It's time to merge this work in. (This work proceeded in parallel at the time because we weren't managing Recline).
Broadening the focus: Recline as data explorer can now be done mainly with external libraries so core is small. This core data visualization is an essential part of a frontend data portal framework. ... And there is a need for data portal frontend framework (see e.g. https://tech.datopian.com/frontend). And finally
Recline was a data exploration and visualization toolkit. However, external developments mean a lot of the core of Recline is now existing elsewhere e.g.
Frictionless for the dataset library and model
Frictionless Views and Vega for declarative graph language
React for the render library.
This means what was old Recline is actually quite small.
Nevertheless this core is an essential part of any data portal system.
So why not expand it to be a full data portal frontend framework (instead of having e.g. a separate portal framework that uses Recline as a library.)
Meanwhile at Datopian we have been built at least three iterations of a frontend framework since 2016 and we can merge this work with Recline.
Recline.js will rename Portal.js, get upgraded and broaden to be a data portal framework (from being a "data explorer" framework).
Overview
What
Why
Recline was a data exploration and visualization toolkit. However, external developments mean a lot of the core of Recline is now existing elsewhere e.g.
This means what was old Recline is actually quite small.
Nevertheless this core is an essential part of any data portal system.
So why not expand it to be a full data portal frontend framework (instead of having e.g. a separate portal framework that uses Recline as a library.)
Meanwhile at Datopian we have been built at least three iterations of a frontend framework since 2016 and we can merge this work with Recline.
In summary: let's broaden Recline to be a complete portal (frontend) framework
How
Acceptance
Tasks
recline
@risenW Done https://github.com/datopian/recline/tree/reclineThe text was updated successfully, but these errors were encountered: