Re:Modular CSS for Web Components ‒ the VCL Is Here
by anonyfox on Wednesday March 30, 2016 @09:38AM
(#11389130)
But with the namespace, you can avoid name collisions. As I see it, VCL components can be used standalone, even when you already use a different UI framework, so this makes sense for me.
Re:Modular CSS for Web Components ‒ the VCL Is Here
by colinramsay on Wednesday March 30, 2016 @10:15AM
(#11389394)
I realise this. It doesn't stop it from being "slightly uglier and slightly more verbose" though :)
You can namespace Bootstrap though [1] so perhaps you can change this VCL convention somehow too.
[1] http://stackoverflow.com/questions/13966259/how-to-namespace...
- Uses camelCase for classes; Foundation and Bootstrap are hyphen separated, as is FontAwesome. This leads to weird examples like the notification one [1] where you have mixed naming conventions.
- All classes in the docs are prefixed with vcl. I guess this is some kind of namespacing, but again BS and Foundation don't have this, and you end up with slightly uglier and slightly more verbose class names.
It doesn't seem like the tabs or drawer examples work for me so it's not clear how it's handling those but it seems that it's not tied to jQuery, which I definitely do like.
[1] http://vcl.github.io/#vcl-notification