Awesome! I’ll add svg.js to the build script.
On 6/18/15, 4:14 AM, "Michael Schmalle" <teotigraphix...@gmail.com> wrote:
>HAHA!
>
>I got the SWC to compile all SVG with only adding these excludes;
>
>config.addExclude("SVGStylable", "className");
>config.addExclude("SVGStylable", "style");
>config.addExclude("SVGLocatable", "farthestViewportElement");
>config.addExclude("SVGLocatable", "nearestViewportElement");
>
>The all 200+ errors boiled down to just these conflicts, that is what I
>get
>for trying to code after ripping out a bathtub and sheetrock. :)
>
>So ALEX, the only thing we need now to have this included in the JS.swc is
>getting it locally to compile, I don't know the rules, so this is in your
>court.
>
>Mike
>
>
>
>
>
>On Thu, Jun 18, 2015 at 6:01 AM, Michael Schmalle
><teotigraphix...@gmail.com
>> wrote:
>
>> @Om code completion stopping has to be a FB things, really nothing to do
>> with the SWC am pretty sure.
>>
>> @Fred The thing that is missing is properties on an interface in SVG.
>>
>> So the properties problem. There are conflicts with SVG super classes
>> where say Element.style is defined as CSSStyleDeclaration and SVGElement
>> implements SVGStylable and overloads it's type.
>>
>> As we all know we can't do this, so the only option to clear this up is
>> for me to go through the massive interface conflicts and add the
>>interface
>> properties as excluded in the compile.
>>
>> @Alex, we still need this file locally during compile, you have a
>>solution
>> for that?
>>
>> Mike
>>
>>
>>
>>
>>
>> On Wed, Jun 17, 2015 at 10:00 PM, Frédéric THOMAS
>><webdoubl...@hotmail.com
>> > wrote:
>>
>>> That's funny, I was playing with JS.swc and wanted to start doing
>>>things
>>> with svg too but didn't find any of its classes, so, I was about to use
>>> CanvasRenderingContext2D but seen our components are done using svg, I
>>> returned on my email to ask about svg in JS.swc and realized it wasn't
>>> updated, refreshed and seen your very great example Om.
>>>
>>> I won't do better, at least for tonight, will anyway test quickly your
>>> new JS.swc version Mike.
>>>
>>> Thanks,
>>> Frédéric THOMAS
>>>
>>>
>>> ----------------------------------------
>>> > From: aha...@adobe.com
>>> > To: dev@flex.apache.org
>>> > Subject: Re: [FlexJS] JS.swc does not seem to have any SVG* element
>>> defintions
>>> > Date: Thu, 18 Jun 2015 00:40:24 +0000
>>> >
>>> > Sweet!
>>> >
>>> > On 6/17/15, 5:31 PM, "OmPrakash Muppirala" <bigosma...@gmail.com>
>>> wrote:
>>> >
>>> >>It works for the most part! At some point, the code completion
>>>stopped
>>> >>working. I am not able to get it back now.
>>> >>
>>> >>But, the good news, here is an interactive US built completely in
>>> >>ActionScript3!
>>> >>
>>> >>Working demo: http://bigosmallm.github.io/flexjs/mapexample/
>>> >>AS3 code: https://gist.github.com/bigosmallm/824147f7c439c584a09b
>>> >>JS code: Who cares? ;-)
>>> >>
>>> >>I will spend some more time building something nicer over the next
>>>day
>>> or
>>> >>so.
>>> >>
>>> >>Thanks,
>>> >>Om
>>> >>
>>> >>On Wed, Jun 17, 2015 at 3:53 PM, OmPrakash Muppirala
>>> >><bigosma...@gmail.com>
>>> >>wrote:
>>> >>
>>> >>> On Wed, Jun 17, 2015 at 3:20 PM, Michael Schmalle <
>>> >>> teotigraphix...@gmail.com> wrote:
>>> >>>
>>> >>>> Well I got it to compile on one condition. I had to turn on the
>>>emit
>>> >>>>props
>>> >>>> and methods for the interfaces.
>>> >>>>
>>> >>>> The actual classes themselves have all the definitions. There are
>>> major
>>> >>>> conflicts with the SVG* interfaces and some base stuff.
>>> >>>>
>>> >>>> Example; Element.style is CSSStyleDeclaration, in SVG it
>>>redeclares
>>> >>>>this
>>> >>>> on
>>> >>>> SVGStylable as a different type.
>>> >>>>
>>> >>>> So Om, I compiled the SWC and just put it on my server for you to
>>> try,
>>> >>>> before I commit anything, you need to see if it works the way you
>>> need.
>>> >>>>
>>> >>>> http://www.teotigraphix.com/assets/JS.swc
>>> >>>>
>>> >>>>
>>> >>> Great! I am on it.
>>> >>>
>>> >>> Thanks,
>>> >>> Om
>>> >>>
>>> >>>
>>> >>>> Mike
>>> >>>>
>>> >>>>
>>> >>>> On Wed, Jun 17, 2015 at 6:16 PM, Alex Harui <aha...@adobe.com>
>>> wrote:
>>> >>>>
>>> >>>>>
>>> >>>>>
>>> >>>>> On 6/17/15, 2:47 PM, "Michael Schmalle"
>>><teotigraphix...@gmail.com>
>>> >>>> wrote:
>>> >>>>>
>>> >>>>>>Ah this is a nasty file to deal with, it's generated from IDL and
>>> >>>>has
>>> >>>>>>10,000 lines with massive interfaces that have to have their
>>> >>>>prototypes
>>> >>>>>>transformed to get/set.
>>> >>>>>
>>> >>>>> I’m not sure I understand the part about prototype
>>>transformation. I
>>> >>>> only
>>> >>>>> saw one get/set pair that could be a property. Lots of .setXXX
>>>calls
>>> >>>> take
>>> >>>>> multiple parameters. Does it make it easier if you don’t have to
>>>do
>>> >>>>the
>>> >>>>> transformation?
>>> >>>>>
>>> >>>>> If you can get this file to convert to AS even procedurally, I’ll
>>> >>>>find a
>>> >>>>> way to get it into the build and JS.swc.
>>> >>>>>
>>> >>>>>>
>>> >>>>>>Who thinks I can do this? Haha
>>> >>>>>
>>> >>>>> If there is anyone who can do it, it would be you ;-)
>>> >>>>>
>>> >>>>> -Alex
>>> >>>>>
>>> >>>>>
>>> >>>>
>>> >>>
>>> >>>
>>> >
>>>
>>>
>>
>>
