Re: [FalconJX] Building CreateJS externs

2015-06-26 Thread Michael Schmalle
On Fri, Jun 26, 2015 at 6:57 PM, Josh Tynjala wrote: > Your description had exactly the right amount of detail to point me in the > right direction. :) > That's what I was aiming for. :) Mike > > - Josh > > On Fri, Jun 26, 2015 at 3:33 PM, Michael Schmalle < > teotigraphix...@gmail.com > > wr

Re: [FalconJX] Building CreateJS externs

2015-06-26 Thread Josh Tynjala
Your description had exactly the right amount of detail to point me in the right direction. :) - Josh On Fri, Jun 26, 2015 at 3:33 PM, Michael Schmalle wrote: > Right on Josh, that is exactly how I would have done it!~ Thanks! > > Mike > > On Fri, Jun 26, 2015 at 6:30 PM, Michael Schmalle < > t

Re: [FalconJX] Building CreateJS externs

2015-06-26 Thread Michael Schmalle
Right on Josh, that is exactly how I would have done it!~ Thanks! Mike On Fri, Jun 26, 2015 at 6:30 PM, Michael Schmalle wrote: > Just to add, you probably figured it out, when I said emitClass(), I meant > all of them, since you can't have any constants, classes, interfaces, enums > or typedef

Re: [FalconJX] Building CreateJS externs

2015-06-26 Thread Michael Schmalle
Just to add, you probably figured it out, when I said emitClass(), I meant all of them, since you can't have any constants, classes, interfaces, enums or typedefs created for external externs. You get the idea. :) MIke On Fri, Jun 26, 2015 at 5:14 PM, Josh Tynjala wrote: > Okay, I looked over

Re: [FalconJX] Building CreateJS externs

2015-06-26 Thread Josh Tynjala
Okay, I looked over the source code. I think I understand how to implement it. I'll give it a shot. Hopefully, I'll have something good to report later today. - Josh On Fri, Jun 26, 2015 at 1:56 PM, Michael Schmalle wrote: > On Fri, Jun 26, 2015 at 4:49 PM, Josh Tynjala > wrote: > > > Yes, tha

Re: [FalconJX] Building CreateJS externs

2015-06-26 Thread Michael Schmalle
On Fri, Jun 26, 2015 at 4:49 PM, Josh Tynjala wrote: > Yes, that makes sense. I incorrectly assumed it knew how to get that > information from SWCs too. > > So, if I understand you correctly, this -external-externs argument doesn't > exist yet? It still needs to be added to externc? > Correct,

Re: [FalconJX] Building CreateJS externs

2015-06-26 Thread Josh Tynjala
Yes, that makes sense. I incorrectly assumed it knew how to get that information from SWCs too. So, if I understand you correctly, this -external-externs argument doesn't exist yet? It still needs to be added to externc? - Josh On Fri, Jun 26, 2015 at 1:29 PM, Michael Schmalle wrote: > Ah! Yes

Re: [FalconJX] Building CreateJS externs

2015-06-26 Thread Michael Schmalle
Ah! Yes, this is a "problem" because to generate the correct AS, we need the extern to be loaded in the closure compiler for my AST resolver to work correctly. So actually, there is no bug, other than you need to supply dependencies to the javascript compiler(Closure Compiler). So, what needs to

Re: [FalconJX] Building CreateJS externs

2015-06-26 Thread Josh Tynjala
1. Yes, but let's take CreateJS out of the equation. It's not necessary to reproduce the error. I created the following nativemouseevent-extern.js: /** * @constructor * @extends {MouseEvent} * @param {string} type * @param {MouseEventInit=} opt_eventInitDict */ function NativeMouseEvent(type

Re: [FalconJX] Building CreateJS externs

2015-06-26 Thread Michael Schmalle
Josh, I am having one of those days, but I still am not quite getting what is happening with the constructor stuff. Can you spell it out one more time with maybe something I can try for myself? 1. So are you saying you are creating a .js file that you are having externc.jar parse and emit for Cr

Re: [FalconJX] Building CreateJS externs

2015-06-26 Thread Josh Tynjala
I actually don't need the typedef stuff right now. I was trying to use the same workaround that the CreateJS TypeScript definitions use to avoid naming conflicts between MouseEvent and createjs.MouseEvent. It creates a fake class named NativeMouseEvent that extends MouseEvent. I was trying to modif

Re: [FalconJX] Building CreateJS externs

2015-06-26 Thread Michael Schmalle
Weird, looking at the generated source; /** * @param type [string] * @param opt_eventInitDict [(MouseEventInit|null|undefined)] * @see [w3c_event] */ public function MouseEvent(type:String, opt_eventInitDict:MouseEventInit = null) { super(null, null); } It'

Re: [FalconJX] Building CreateJS externs

2015-06-26 Thread Josh Tynjala
Yeah, I think metadata would be acceptable too. If that seems easier to you, I say let's do that. I just found another issue in externc. I tried to subclass MouseEvent, which is compiled into js.swc. It's not correctly determining the number of constructor arguments for MouseEvent, so when I try t

Re: [FalconJX] Building CreateJS externs

2015-06-26 Thread Michael Schmalle
1) That is a bug, I think I hard-coded a quick fix on things that have a @template tag and I immediately transformed them to Object without checking the for optional or var arg declarations. I can fix this, it's only methods with that tag and there are no very many. 2) Yeah, I figured as much, I h

Re: [FalconJX] Building CreateJS externs

2015-06-25 Thread Alex Harui
On 6/25/15, 5:06 PM, "Josh Tynjala" wrote: >2) I immediately ran into that issue where a top-level class interferes >with a class that has the same name in a package. w3c_event.js defines the >top-level Event class, and CreateJS has a createjs.Event class. It's the >exact same issue that you bro

Re: [FalconJX] Building CreateJS externs

2015-06-25 Thread Alex Harui
Josh, in your scenario do you ever need the top level event? Sent from my LG G3, an AT&T 4G LTE smartphone -- Original message-- From: Josh Tynjala Date: Thu, Jun 25, 2015 5:07 PM To: dev; Subject:[FalconJX] Building CreateJS externs Hey Mike, I finally got a chance to s

[FalconJX] Building CreateJS externs

2015-06-25 Thread Josh Tynjala
Hey Mike, I finally got a chance to start playing around with some of your work today. I've been starting out with externc. I've run into a couple of issues. One you already know about. Let's start with the other one, though... 1) It looks like the Array class constructor has the wrong signature.