See here: https://github.com/ember-vcl
All these components make use of the VCL. The integration is bassically CSS class names. And more formally, you can add a dependncy to the required NPM packages. However, we did not do this yet in the Ember VCL.
Because the whole idea of the VCL is to be JS-less and thus logicless. We want to leave this to Ember, Angular, React etc. That's why we are framework agnostic.
Because they not neither modular and thus it's not possible to integrate them with sound package management systems like NPM, bower etc. You can only get the whole blob, with the VCL you can depend on a set of fine grained CSS modules.
- 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.
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.
I think they were pointing out that VCL (Visual Component Library) is already a name used by Borland / Embarcadero Delphi Pascal for their cross-platform UI toolkit.
At first, I thought this was something similar to CSS Modules (which, btw solved mostly all my grievances with packaging CSS in a large application), but this is something much more akin to Bootstrap or Foundation.