On 4/1/13 3:44 PM, "Om" <[email protected]> wrote:
> On Mon, Apr 1, 2013 at 1: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.
>>
>
> I see that the AS side is pretty bare for the html5 controls. Do you or
> Peter have any thoughts on how I can proceed? What would be a good entry
> point for me?
> Obviously adding skinning support to the AS side would be the first step.
> I would rather let you guys build a very simple example and I can
> hopefully take it from there.
I think the first step is to understand how it works in pure JS, then look
at what it will take to replicate that in AS.
I've been trying to read up on SVG skinning for HTML5. I'm not finding a
whole lot. It appears that there are no new APIs on any components and it
is just that the background-image CSS property can now point to svg files.
If that's true, then we need to finish up a CSS implementation in FlexJS,
and teach FalconJX to output the right .css file. Then the AS components
need to leverage that CSS lookup to determine what FXG file to use. In
theory, the JS side will "just work". Thinking about that a bit more, it
might be necessary to have an SVG->FXG transform in AS so both the AS and JS
can pull in .svg files.
I think I saw something about "embedded SVG" so we need to understand how
that works as well.
I also want to know more about how JS can manipulate the SVG and how you
plan to manage any AS in an existing skin.
And I'm still not sure that it is right to set expectations that we can
transform existing Spark Skins because they composite other components. It
might be best to require the input to be legitimate fxg files. Some other
tool or part of the workflow might be able to pull as much fxg from an skin
file.
BTW, if you haven't please read http://www.w3.org/TR/components-intro/
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
