On Mon, Apr 1, 2013 at 3:33 PM, Alex Harui <[email protected]> wrote: > Good progress! > > You may have seen that Peter checked in an HTML5 control set. Now we have > to figure out how to wire your stuff into that. > > Some comments: > 1) How should an svg button skin handle the button states in html? It > isn't > done with separate svg files? >
At one point I was looking into skins that were basically swapping FXG assets: <s:SparkButtonSkin xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" xmlns:fb="http://ns.adobe.com/flashbuilder/2009" minWidth="21" minHeight="21" alpha.disabled="0.5"> <!-- FXG assets --> <s:UpSkin left="-1" right="-1" top="-1" bottom="-1" includeIn="up"> <s:OverSkin left="-1" right="-1" top="-1" bottom="-1" includeIn="over"> <s:DownSkin left="-1" right="-1" top="-1" bottom="-1" includeIn="down"> <s:DisabledSkin left="-1" right="-1" top="-1" bottom="-1" includeIn=" disabled"> <!-- states --> <s:states> <s:State name="up" /> <s:State name="over" /> <s:State name="down" /> <s:State name="disabled" /> </s:states> </s:SparkButtonSkin> That's basically what Om is doing in the HTML controls. Thinking out loud here but if a compiled FXG is basically raw FP drawing commands then could the same thing be happening with SVG inside the browser? > 2) I would think we would want to use CSS more. I forgot to follow up with > Jude on his objections to CSS proliferation. Maybe he'll jump in here. > I had a couple concerns but you'll have to see if they apply here. Using SVG to draw the graphics to the background solves some of the concerns I had.
