Playground UI

[saurabhdaware]

We can start off by adding css to the existing playground. Let's have a discussion here about the UI design.

[ovbm]

Hey there, yes, I think the styling needs to be improved. I'd like to couple this with #161 . Also we could think about working with a component library or a UI framework to make the code easy to maintain and collaborate.
Material UI is very well maintained and stable: https://material-ui.com/

[ovbm]

didn't mean to close ^^

[saurabhdaware]

What are the features that we're going to have in the playground (apart from the ones that exist right now?)

If you want something lightweight then I think Preact or Svelte can be good options as well or we can even think of just staying vanilla (if we just want to replicate the existing features)

[ovbm]

There are two main features we want to prioritize:

• Create output table directly in the playground #158
• Create error logs and warnings component in dev playground #159

could be done vanilla, just thinking about the future really.

[ovbm]

i'm going to be implementing react ASAP so we can use things like react-table and other useful components.

[saurabhdaware]

Yeah I think react will be better in the long run (specially for something like #160 ).

You can let me know if there is anything I can help with.

[ovbm]

React transition is done, UI is still very crude, but If you want to have a go, feel free to make suggestions. The table component could be paginated for example.

[saurabhdaware]

Cool, I'll check it out. Also, there are some dependencies which are mentioned in babel-config but are not mentioned in package.json so they were throwing errors when I followed installation step. I've added them to package.json and I'll create PR in some time.

[martincollignon]

closing due to inactivity. A couple of improvements have already been made. @madsnedergaard @corradio