flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From OmPrakash Muppirala <bigosma...@gmail.com>
Subject Re: [FlexJS] Building SVG skins from existing Spark component skins
Date Thu, 27 Feb 2014 22:38:45 GMT
On Thu, Feb 27, 2014 at 1:43 PM, Alex Harui <aharui@adobe.com> wrote:

>
>
> On 2/27/14 11:53 AM, "OmPrakash Muppirala" <bigosmallm@gmail.com> wrote:
>
> >
> >Lets do it!  Where do we start?  I want to start building some JS side SVG
> >drawing APIs that I want to use with our Charts.  The BarChart on the JS
> >side uses CSS to draw, which will become limited very soon.  Having a
> >robust JS based SVG drawing API will definitely help us in the long run.
> >Do you mind starting with an SVG parser in Falcon?  We could just do with
> >the primitives for now:  BitmapImage, Ellipse, Line, Path and Rect.  Then
> >we can do the fills, strokes, gradients, etc.  No need to deal with the
> >whole SVG spec.
>
> An SVG Parser or emitter (output to SVG from the tree)?  I'll try to find
> the relevant code this evening.
>
> I'm not sure what you mean by a drawing library.  What pops into my mind
> is a component called Graphics that creates a DOM element and draws Flash
> in AS and SVG in JS.  You shouldn't need any compiler changes for that.
>
>
The Graphics component is what I had in my mind.  I thought you had
mentioned some compiler changes in your last email.  If that is not
required, ignore what I said.

If I understand the flow correctly, we will have an AS skin class that
references an SVG document.  The compiler parses the SVG document (like it
does with FXG today) and will generate AS code that uses the Graphics
component to draw stuff in Flash.

On the JS side, we will have a similar Graphics component with same drawing
API, except that the code draws SVG onto the HTML DOM.

I believe you will figure out the SVG parser part.  I can take care of
creating the Graphics component on AS and JS versions.

Am I on the right track?

Thanks,
Om


> -Alex
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message