Removing the MaterializeCSS dependency

[GermaVinsmoke]

There isn't much use of MaterializeCSS, so it's better to remove it.

[Erick2280]

Hi! I'll take this issue :)

[GermaVinsmoke]

Alright, thanks for the help. I added travis ci for auto-deployment, I hope it'll help.

[nuwan94]

Hi, Can I take this issue?

[GermaVinsmoke]

Yeah @nuwan94

[CmdEngineer]

@nuwan94 still on it?
EDIT: If not can I take it?

[GermaVinsmoke]

Will it be better to use .css files or better go with styled-components?

[CmdEngineer]

I dont know

[CmdEngineer]

@nuwan94 still on it?
EDIT: If not can I take it?

Still asking @nuwan94

[GermaVinsmoke]

Repo isn't even forked by him, so you can do it @CmdEngineer

[CmdEngineer]

Alright

[CmdEngineer]

@GermaVinsmoke
Apparently MaterialCSS does have a big usage:

Buttons and the graph are unaffected

[GermaVinsmoke]

The main thing is materialize-css grid -
className="container"
className="row"
className="col "
I think we can use flexbox instead of this.
A lot of things will be solved with the help of flexbox.

The other thing is className="card". So, for this, I think it'll be better to use styled-components coz reusable Card component.

Removing materialize-css as it is having some security issues and I think we don't need it as it is having a size of 175kB (minified) and styled-components is having a size of 45kB (minified).

[CmdEngineer]

materialize-css as it is having some security issues
how does css introduce security issues?

[CmdEngineer]

Suggestion: maybe use Spectre?

[GermaVinsmoke]

materialize-css as it is having some security issues
how does css introduce security issues?

Three of its javascript component are having vulnerabilities and there's no patch fix for that 🤔. So, if we're not using any of the JS Components then why to keep a module of that big size. I think that Spectre.css is cool and it'll work.