There are a few non-standard DOM extensions here:
https://github.com/google/closure-compiler/blob/master/externs/ie_dom.js
(depends on w3c_dom2.js)
https://github.com/google/closure-compiler/blob/master/externs/gecko_dom.js
(depends on w3c_dom2.js)
https://github.com/google/closure-compiler/blob/m
BTW, I just ran my asdoc tool on every project in flex-asjs and it only
took 10 seconds(parse, analyze, render), this uses fully configurable
Velocity templates instead of XSL.
http://snag.gy/EOIuW.jpg
Mike
On Fri, Jun 5, 2015 at 3:31 PM, Michael Schmalle
wrote:
> Alex! I just pulled the chang
Alex! I just pulled the changes you made and rebuilt Falcon code base and
parsers.
I just ran my asdoc tool on the flex-asjs repo, I think another screenshot
is in order. :)
http://snag.gy/TDXfe.jpg
Mike
On Fri, Jun 5, 2015 at 3:06 PM, Alex Harui wrote:
> I just pushed a change that seems to
On Fri, Jun 5, 2015 at 8:42 AM, Michael Schmalle
wrote:
> This is what I am into right now; :)
>
>
> visitScript
> 239ASSIGN 0 58
> 239 GETPROP 0 21
> 239GETPROP 0 15
> 239 NAME 0 5 Array
> 245 NAME 6 9 prototype
> 255NAME 16 5 ev
On Fri, Jun 5, 2015 at 8:31 AM, Alex Harui wrote:
>
>
> On 6/5/15, 8:18 AM, "OmPrakash Muppirala" wrote:
>
> >On Jun 5, 2015 3:12 AM, "Michael Schmalle"
> >wrote:
> >>
> >> @Om ... SVG, this should get you excited. :)
> >>
> >> http://snag.gy/xEpfa.jpg
> >>
> >> Mike
> >
> >Fantastic! What a
I just pushed a change that seems to get ASDoc working. There was a rule
that looked like it tried to eliminate double-spaces and somehow the lexer
ended up there at the end of string instead of thinking it was done.
I have no idea what that was for since the output currently seems to
capture lin
This is what I am into right now; :)
visitScript
239ASSIGN 0 58
239 GETPROP 0 21
239GETPROP 0 15
239 NAME 0 5 Array
245 NAME 6 9 prototype
255NAME 16 5 every
263 FUNCTION 24 34
272NAME 9 8 callback
282
On 6/5/15, 8:18 AM, "OmPrakash Muppirala" wrote:
>On Jun 5, 2015 3:12 AM, "Michael Schmalle"
>wrote:
>>
>> @Om ... SVG, this should get you excited. :)
>>
>> http://snag.gy/xEpfa.jpg
>>
>> Mike
>
>Fantastic! What a great way to stay the day :-)
>
>When will we able to start testing all this?
On Jun 5, 2015 3:12 AM, "Michael Schmalle"
wrote:
>
> @Om ... SVG, this should get you excited. :)
>
> http://snag.gy/xEpfa.jpg
>
> Mike
Fantastic! What a great way to stay the day :-)
When will we able to start testing all this?
Thanks,
Om
>
> On Fri, Jun 5, 2015 at 6:02 AM, Michael Schmall
@Om ... SVG, this should get you excited. :)
http://snag.gy/xEpfa.jpg
Mike
On Fri, Jun 5, 2015 at 6:02 AM, Michael Schmalle
wrote:
> BTW I need to brush up on canvas but I see;
>
> So I assume the HTMLCanvasElement.getContext() passes a
> CanvasRenderingContext2D correct?
>
> I can't wait to g
BTW I need to brush up on canvas but I see;
So I assume the HTMLCanvasElement.getContext() passes a
CanvasRenderingContext2D correct?
I can't wait to get out of this compiler stuff and actually try to test
some of this stuff in the browser. :)
Mike
public class CanvasRenderingContext2D {
...
On Fri, Jun 5, 2015 at 12:39 AM, OmPrakash Muppirala
wrote:
> Fantastic work, Mike!
>
> I dont see any SVG elements, is that part of something other spec?
>
Haven't got that far yet, was busy getting inheritance and edge cases fixed
with the base DOM stuff.
I have looked through the closure/ex
Fantastic work, Mike!
I dont see any SVG elements, is that part of something other spec?
On that line, how would one get Canvas, Webgl, etc.?
Thanks,
Om
On Jun 4, 2015 5:31 PM, "Josh Tynjala" wrote:
> Agreed! Great stuff, Mike.
>
> - Josh
>
> On Thu, Jun 4, 2015 at 2:07 PM, Alex Harui wrote
Agreed! Great stuff, Mike.
- Josh
On Thu, Jun 4, 2015 at 2:07 PM, Alex Harui wrote:
> Amazing!
>
> On 6/4/15, 2:04 PM, "Michael Schmalle" wrote:
>
> >Well so far I have got the below compiling into .as classes and interfaces
> >using the following externals files;
> >
> >There is a definite or
You da man! We’ll see how well I do with the ASDoc lexer. I am set up to
debug it now.
-Alex
On 6/4/15, 2:21 PM, "Michael Schmalle" wrote:
>I think I have mastered parsing AST. :) This took me one day to do from
>downloading Rhino and never using it to what you see now. hahah
>
>Mik
>
>On Thu
I think I have mastered parsing AST. :) This took me one day to do from
downloading Rhino and never using it to what you see now. hahah
Mik
On Thu, Jun 4, 2015 at 5:18 PM, Alex Harui wrote:
> Also amazing!
>
> On 6/4/15, 2:14 PM, "Michael Schmalle" wrote:
>
> >Check out the screen shot;
> >
>
Also amazing!
On 6/4/15, 2:14 PM, "Michael Schmalle" wrote:
>Check out the screen shot;
>
>http://snag.gy/XyytR.jpg
>
>Inheritance and everything is working. :)
>
>Mike
>
>On Thu, Jun 4, 2015 at 5:07 PM, Alex Harui wrote:
>
>> Amazing!
>>
>> On 6/4/15, 2:04 PM, "Michael Schmalle"
>>wrote:
>>
>
Check out the screen shot;
http://snag.gy/XyytR.jpg
Inheritance and everything is working. :)
Mike
On Thu, Jun 4, 2015 at 5:07 PM, Alex Harui wrote:
> Amazing!
>
> On 6/4/15, 2:04 PM, "Michael Schmalle" wrote:
>
> >Well so far I have got the below compiling into .as classes and interfaces
>
Amazing!
On 6/4/15, 2:04 PM, "Michael Schmalle" wrote:
>Well so far I have got the below compiling into .as classes and interfaces
>using the following externals files;
>
>There is a definite order these need to be parsed in, I am still figuring
>them out. I plan on adding in the asdocs, the ver
Well so far I have got the below compiling into .as classes and interfaces
using the following externals files;
There is a definite order these need to be parsed in, I am still figuring
them out. I plan on adding in the asdocs, the version of JS the API was
introduced in.
Mike
html5.js
missing.j
Yeah sorry to confuse you, the Velocity stuff doesn't matter, for that
matter my asdoc framework I wrote doesn't(it was just showing I had all
this working in the context of Falcon), we just need the ASDocTokenizer to
tokenize the comment data given to the ASDocDelegate.
Mike
On Thu, Jun 4, 2015
The way I did it was, I did exactly what you did, implemented the
ASDocDelegate and saved the tokes as it parsed all the files.
Then I used the token String like you in the ASDocTokenizer to parse the
loop I showed you above.
I would add the DocTag and stuff if you can get the ASDocTokenizer work
For this exercise though, we don’t care about the output as Velocity or
XSL right? All you want is ASDocTokens in the AST? IIRC, in Falcon you
retrieve ASDoc comments via node.getASDocComment() and get an ASDocComment
instance. Do you want the Token to be the root of a mini-tree of parsed
nodes?
I actually wrote a WHOLE NEW asdoc program that uses Apache Velocity
templates instead of XSL.
That DocTag is my class.
Mike
On Thu, Jun 4, 2015 at 2:45 PM, Alex Harui wrote:
> I don’t see any signs of ASDoc support in flex-falcon. I see
> ASDocTokenizer and ASDocToken, but no ASDOC.java that
I don’t see any signs of ASDoc support in flex-falcon. I see
ASDocTokenizer and ASDocToken, but no ASDOC.java that would be equivalent
to MXMLC.java and have a main() method. The current Flex SDK has an
ASDoc.jar. Shouldn’t we have these pieces? Do you have them around
somewhere? Otherwise I w
> I think IIRC, I actually tried a simple test case and it would work.
I meant wouldn't work, I could not get it to work ever.
Mike
On Thu, Jun 4, 2015 at 2:36 PM, Michael Schmalle
wrote:
> BTW, the loop always happens at the VERY end of the comment, so when you
> get to the end the(the last c
BTW, the loop always happens at the VERY end of the comment, so when you
get to the end the(the last call of next() that should return null);
tok = tokenizer.next();
never returns, it gets stuck trying to exit.
Mike
On Thu, Jun 4, 2015 at 2:34 PM, Michael Schmalle
wrote:
> I posted about this
I posted about this a couple weeks ago and I tried recompiling with JFlex
1.5 I think, the older version and still had the problem.
Maybe I messed up something but I tried with my same asdoc code when I
fixed the build for the FlexJS asdocs. I wanted to see it work with my
version of a documentor.
On 6/4/15, 11:23 AM, "Michael Schmalle" wrote:
>>Hmm. Maybe I should spend some time looking into fixing ASDocTokenizer?
>> Was the problem that it didn’t work on every AS file we current have?
>>
>
>
>It doesn't work on anything, there is an infinite loop in the scanner that
>is created by JFl
On Thu, Jun 4, 2015 at 2:11 PM, Alex Harui wrote:
>
>
> On 6/4/15, 10:31 AM, "Michael Schmalle" wrote:
> >>If you mean the AS package for the classes in these SWCs, I have to admit
> >> I was a bit surprised to see in the AS output example that Document in a
> >> “dom” package. I would think th
On 6/4/15, 10:31 AM, "Michael Schmalle" wrote:
>>If you mean the AS package for the classes in these SWCs, I have to admit
>> I was a bit surprised to see in the AS output example that Document in a
>> “dom” package. I would think these two SWCs would not have their
>>classes
>> in any AS packa
On Thu, Jun 4, 2015 at 1:20 PM, Alex Harui wrote:
>
>
> On 6/4/15, 9:53 AM, "Michael Schmalle" wrote:
>
> >Yeah to be honest my main concern was these SWCs. When I started testing
> >the emitter for DOM stuff like I showed the other day, I couldn't
> >"believe"
> >in it because I was using the R
On Thu, Jun 4, 2015 at 1:28 PM, Josh Tynjala wrote:
> As far as packages go, I think if a class is top-level in JavaScript, it
> should be the same in ActionScript. At least by default.
>
>
I only added the dom because I wasn't really thinking about it.
What about local name collisions with user
As far as packages go, I think if a class is top-level in JavaScript, it
should be the same in ActionScript. At least by default.
- Josh
On Thu, Jun 4, 2015 at 10:20 AM, Alex Harui wrote:
>
>
> On 6/4/15, 9:53 AM, "Michael Schmalle" wrote:
>
> >Yeah to be honest my main concern was these SWCs.
On 6/4/15, 9:53 AM, "Michael Schmalle" wrote:
>Yeah to be honest my main concern was these SWCs. When I started testing
>the emitter for DOM stuff like I showed the other day, I couldn't
>"believe"
>in it because I was using the Randori stuff.
>
>Now with this, the first step is actually real a
Yeah to be honest my main concern was these SWCs. When I started testing
the emitter for DOM stuff like I showed the other day, I couldn't "believe"
in it because I was using the Randori stuff.
Now with this, the first step is actually real and under the project's
control, all of it.
1. I'm going
This is great! Now we can generate those SWCs. I’ll go worry about
something else now.
Thanks,
-Alex
On 6/4/15, 9:25 AM, "Michael Schmalle" wrote:
>BTW, if you are looking at the generated AS, there are some errors int he
>arguments that I have already fixed. :) Like Number, Number, Number et
BTW, if you are looking at the generated AS, there are some errors int he
arguments that I have already fixed. :) Like Number, Number, Number etc.
Mike
On Thu, Jun 4, 2015 at 12:23 PM, Michael Schmalle wrote:
>
>
> On Thu, Jun 4, 2015 at 12:19 PM, Alex Harui wrote:
>
>> Awesome!
>>
>> So we ca
On Thu, Jun 4, 2015 at 12:19 PM, Alex Harui wrote:
> Awesome!
>
> So we can forget d.ts files and IDL files, right? Plus at least
> w3c_dom1.js is Apache Licensed.
>
The way I set up the parser/emitter is we can merge things using the same
model but parsing different files. For instance;
w3c_e
Alex,
es3.js and es5.js from the same directory look pretty promising:
https://github.com/google/closure-compiler/blob/master/externs/es3.js
https://github.com/google/closure-compiler/blob/master/externs/es5.js
- Josh
On Thu, Jun 4, 2015 at 9:19 AM, Alex Harui wrote:
> Awesome!
>
> So we can
Awesome!
So we can forget d.ts files and IDL files, right? Plus at least
w3c_dom1.js is Apache Licensed.
I was actually going to spend some time today on the JS primitives swc
(Number, String, Array). Have you seen any externs file for those? I
doubt it exists.
-Alex
On 6/4/15, 8:12 AM, "Mic
Hey,
Well I am a gluten for punishment but, I love parsers and translations so
without further ado;
>From this source file;
https://github.com/google/closure-compiler/blob/master/externs/w3c_dom1.js
I am creating the following ActionScript, long but worth looking at. :)
I found a lot of extern
42 matches
Mail list logo
