@barbushin opened this Pull Request on June 30th 2015 Contributor

There is a popular conflict between Angular and iCheck. I tried different solutions, like using custom derective for iCheck https://github.com/fronteed/iCheck/issues/62, but it does not helps.

I think for now we can just disable iCheck for that Angular form.

Closes #8247

@tsteur commented on July 1st 2015 Owner

Nice! Hopefully we can get rid of iCheck at some point. It always causes problems...

@tsteur commented on July 6th 2015 Owner

Just FYI: Google released a lite version of material design which could be used as an alternative for iCheck see eg http://www.getmdl.io/components/index.html#toggles-section . It also provides nice switches etc

@mattab commented on July 8th 2015 Owner

Nice! Hopefully we can get rid of iCheck at some point. It always causes problems...

definitely, we had so many bugs because of iCheck!

Just FYI: Google released a lite version of material design which could be used as an alternative for iCheck

This looks great, shall we migrate to it?

@barbushin commented on July 8th 2015 Contributor

I'm a big fan of Material Design, and https://github.com/google/material-design-lite is really great. But there is a huge work to migrate, I think. May be we should ask some professional front end developer to estimate this kind of migration?

Regarding building complex interactive Web applications, I think that there should be professional front-end programmer with relative experience.

@tsteur commented on July 9th 2015 Owner

This would be only about checkboxes, radio, and switches. Not a whole redesign. We're doing the whole redesign more or less step by step

This Pull Request was closed on July 1st 2015
Powered by GitHub Issue Mirror