>> So, I need to research more about how skinning works in HTML5, but I have
> >> this vague recollection that skins in HTML5 are entirely graphics. > > > > > > I dont think so. SVG is part of the HTML5 spec now, so what we are doing > > is completely legitimate. > That's sort of what I meant. I think a skin in HTML5 doesn't have > sub-components, and is a bitmap or SVG. > Ah, got it. I dint read your sentence that way earlier. > >> I also need to understand how an HTML5 button skin changes its visuals > with > >> hover/down/selected/focused/emphasized. That would also educate how we > set > >> up a skinning model for FlexJS. > >> > > > > Here is an example: http://demos.madeinthenorth.com/slicker-buttons/# > > Notice how they use SVG in IE9 and CSS3 for Firefox and Webkit. This > also > > shows how to use CSS to control the various states. > I took a look at this post. It uses the "hover" pseudo selector as > expected. > But the button did not have support for things like focused and emphasized. > > > If you can share some examples you like, that would be useful for me. > > > > > > > A restriction on skins to not have sub-components would be great IMHO. A > > new suffix would be great as well. One more modification from our > current > > spark skins would be to perhaps have a HostInterface instead of a > > HostComponent in skins. > > > Actually, I don't envision any sort of HostInterface or HostComponent > contract for skins. The actual skins shouldn't really know anything about > the host. The view bead, which sets up the sub-componentry for the visuals > may bind to the component's model. In that case, it should bind to an interface of the component's model and not any specific implementation. Thanks, Om
