Consider renaming CoreCatelog to reflect these are Material widgets.

[sethladd]

The core catalog is really a catalog of Material widgets. This is probably mixing two things.

I think there are two things here:

A) a core set of logical UI elements: check box, radio button, etc. This is not design language specific, these are core logical widgets we should expect to be always available.

B) an "out of the box" implementation of the logical UI elements, which in our case is the "core catalog" of Material widgets

We should consider creating two concepts more clearly. And, we should consider CoreCatalog to be more like a "MaterialCatalog", so it's more obvious what it is. And , if we create the "logical UI elements" concept, then it should be easier for an app to choose their own implementation of those logical UI elements.

[jacobsimionato]

I agree with this. The idea is to separate the API of the components from their implementation. We should consider this at the A2UI level, as an escape hatch to let people implement standard catalog renderers however they want.

Re Material: I think we should not brand our standard implementation as a Material version because it's not strictly Material, and with A2UI, the aim is to go for a pretty generic, unopinionated rendering style.

[sethladd]

as a Material version because it's not strictly Material

tell me more about this? Looking at the implementation, the implementation of our core catalog are the material widgets from the material package.

I agree with this. The idea is to separate the API of the components from their implementation.

woot!