Should all components be namespaced?

[necolas]

See original plan in #8

I think I ended up wanting SUIT components to seamlessly blend into application code, but there might be some benefit to using the suit- prefix.

[jaredhanson]

I'm in favor of no suit- prefix for the core SUIT components. Since SUIT forms the foundational layer of a project, I think it has the right to claim the "root" namespace. Non-core stuff built on top should namespace itself as necessary.

I've also been toying with the idea of a more Cocoa-esque namespacing method, where you'd pick a two or three capitalized letters to denote your custom components. For example:

JHTableView
JHTableView--mini

My two cents.

[necolas]

I'm not convinced of the readability of names like TWTTweet over than twt-Tweet.

There's also an intentional nod to the current requirement for Web Component custom elements: that the tag name must contain a hyphen. But, I'm ok with the components provided by the core SUIT framework not being namespaced. There aren't many of them and it leaves people to build up their application's components (namespaced) following the same methodology.

[necolas]

Since SUIT forms the foundational layer of a project, I think it has the right to claim the "root" namespace.

Yeah I think I'll go with this for now. The framework comes with some generic components but they don't have to be used.