Needs UIView component

[pinkhominid]

Hey @nkabrown, thanks again for kicking this off. Had thoughts of attempting this a few years back and never got past step 1) Create repo.

So now that the minimal example is running. It seems the next move is a UIView component. I was trying to figure out what this would entail. There are a few items that the other existing UIViews (NG1, NG2+, React) seem to address to varying degrees.

• Unnamed views
• Named views
• Multiple views
• Nested views
• Passing resolve data to transcluded elements/components
• Hooks
• Transition animations
• Other hard to deduce stuff that might be framework specific

Obv not all these are required and I've sort of ordered them in terms of basic priority. I figure this ticket is a good place to discuss. Thoughts?

[nkabrown]

This is a great start. I'm pretty solid on base classes and subclassing but don't have much experience with custom elements. So I'm reading the spec. Don't know enough about the shadow DOM to have a view on whether it's needed, so need to do more research. I'm paying special attention to the custom element lifecycle callbacks.

Was thinking a bit about driving those two lane state highways through the state forests of Northern Michigan when I was naming the repo. They often have a pull off for scenic views or roadside vistas every now and then. I propose we name our custom component ui-vista as a nod to that for fun and just for now. Let me know what you think?

[pinkhominid]

ui-vista, I like it. I may have some time this weekend to take a first pass at this.