Circular progress: 4 colour support

[berenddeboer]

The 4 colour version is not implemented.

[umohm1]

Would like to pick this up but I'm having trouble compiling after following along with the ReadMe.

[berenddeboer]

We'll need a bit more! What error messages, what have you tried, what are you even compiling? You probably should be compiling the demo.

[umohm1]

After completing the install under building instructions running make build-demo leaves me w/ the following error.
make: *** No rule to make target 'build-demo'. Stop.

[berenddeboer]

What does simply running make do?

What's your OS/shell?

[berenddeboer]

Are you actually in the created elm-mdc directory? What's the output of ls?

[umohm1]

Running make gives me the same output as make build-demo.

mkdir -p build
rsync -r demo/images build
cp demo/page.html build/index.html
cp material-components-web.css build/
cp demo/styles/main.css build/main.css
cp elm-mdc.js build/
(cd demo; elm make --optimize Demo.elm --output ../build/demo.js)
Success!     

    Demo ───> ../build/demo.js

On macOS and ls output is

CHANGELOG.md                    demo                            package-lock.json
CONTRIBUTING.md                 elm-mdc.js                      package.json
LICENSE.md                      elm.json                        shell.nix
Makefile                        examples                        src
README.md                       img                             webpack.config.js
build                           material-components-web.css
build.cmd                       node_modules

[berenddeboer]

Confused, you wrote the error was:

make build-demo leaves me w/ the following error.
make: *** No rule to make target 'build-demo'. Stop.

but the above example you gave says it compiles fine, and that it was the same as make build-demo, so doesn't that mean everything is working? Once you have the demo, you can access it with the browser. I don't think you can open the file and elm reactor won't work with these kind of programs, so what I usually do is create a new virtual host .conf file (I'm using Apache).

Writing this I agree this is possibly harder than it could be, there should be some kind of nodejs http server which could serve this and make this step a bit easier.

Anyway, if you serve the demo with Apache or nginx you should be able to continue.