flex.apache.org
Betreff: Re: AW: AW: AW: git commit: [flex-asjs] [refs/heads/develop] -
downloads.xml: goog/bootstrap/nodejs.js is required for node.js support
On 7/15/16, 9:56 AM, "Christofer Dutz" wrote:
>
>Regarding the compile time, I have noticed several times that is is ofte
On 7/15/16, 9:56 AM, "Christofer Dutz" wrote:
>
>Regarding the compile time, I have noticed several times that is is often
>several times faster to read static resources from a jar using the
>classloader than manually accessing a file on disk. So I wouldn't be sure
>that using the jar is a perf
degradation.
Chris
Von: Alex Harui
Gesendet: Freitag, 15. Juli 2016 16:20:23
An: dev@flex.apache.org
Betreff: Re: AW: AW: git commit: [flex-asjs] [refs/heads/develop] -
downloads.xml: goog/bootstrap/nodejs.js is required for node.js support
IMO, if the Maven build pulls GCL from a public repo (no
meinem Samsung Galaxy Smartphone gesendet.
>
>
> Ursprüngliche Nachricht
>Von: Josh Tynjala
>Datum: 15.07.16 15:58 (GMT+01:00)
>An: dev@flex.apache.org
>Betreff: Re: AW: git commit: [flex-asjs] [refs/heads/develop] -
>downloads.xml: goog/bootstrap/nodejs.js is required
: git commit: [flex-asjs] [refs/heads/develop] - downloads.xml:
goog/bootstrap/nodejs.js is required for node.js support
That's exactly what I was referring to. The downloads script downloads
"Google Closure Library". It deletes most of the library, but it didn't in
the
.org
Betreff: Re: git commit: [flex-asjs] [refs/heads/develop] - downloads.xml:
goog/bootstrap/nodejs.js is required for node.js support
FYI: I added goog/bootstrap/nodejs.js to the subset of GCL that we keep. It
is required to continue supporting Node.js as a target.
Chris, I assume that the M
: dev@flex.apache.org
Betreff: Re: git commit: [flex-asjs] [refs/heads/develop] - downloads.xml:
goog/bootstrap/nodejs.js is required for node.js support
FYI: I added goog/bootstrap/nodejs.js to the subset of GCL that we keep. It
is required to continue supporting Node.js as a target.
Chris, I assume
anches:
> refs/heads/develop bf65776b6 -> 84e8ce50b
>
>
> downloads.xml: goog/bootstrap/nodejs.js is required for node.js support
>
>
> Project: http://git-wip-us.apache.org/repos/asf/flex-asjs/repo
> Commit: http://git-wip-us.apache.org/repos/asf/flex-asjs/commit/84e8ce50
>
Here:
http://apache-flex-development.247.n4.nabble.com/Node-js-support-td50414.html
Or here: http://mail-archives.apache.org/mod_mbox/flex-dev/201512.mbox/browser
The Flex website has links to the archives here:
http://flex.apache.org/community-mailinglists.html
On Dec 3, 2015, at 11:02 AM
This mailing list is mirrored as a Nabble user forum. Sometimes folks post
from the Nabble forum directly, which comes with a link in the footer.
To access the forum, simply go to this url: s.apache.org/flex-dev-forum
You should see all the recent threads there.
Thanks,
Om
P.S. The users@ for
Sorry to interject but how do I get a link to this thread? I've seen them
in footers before but not this one.
On Wed, Dec 2, 2015 at 3:29 PM, Josh Tynjala wrote:
> Got it. So if I were trying to hide a require() call, @flexjsignorecoercion
> could be used in my code without requiring users to do
Got it. So if I were trying to hide a require() call, @flexjsignorecoercion
could be used in my code without requiring users to do anything. I think I
may be able to work with that. I'll play around with it, when I have a
moment.
- Josh
On Wed, Dec 2, 2015 at 3:10 PM, Alex Harui wrote:
> Curren
Currently it works at the method's ASDoc, not at the class level.
Here's an excerpt:
/**
* @flexjsignorecoercion org.apache.flex.core.WrappedHTMLElement
* @flexjsignorecoercion HTMLBodyElement
*/
COMPILE::JS
override public function star
Interesting... I didn't know about that. How would @flexjsignorecoercion be
used? In the asdocs for a class, like this?
/**
* @flexjsignorecoercion
*/
public class MyClass {}
If I'm understanding your correctly, when using this tag, the JS output
would not pass the value to Language.as()?
//as
On 12/2/15, 2:37 PM, "Josh Tynjala" wrote:
>Oh, I see. I didn't realize that you were thinking that users would import
>something and also manually call require(). In that case, yes, you could
>still potentially have proper type checking.
>
>I like the idea of using some kind of wrapper class t
Oh, I see. I didn't realize that you were thinking that users would import
something and also manually call require(). In that case, yes, you could
still potentially have proper type checking.
I like the idea of using some kind of wrapper class to hide the require()
call. It's kind of messy to bot
On 12/2/15, 12:12 PM, "Josh Tynjala" wrote:
>You'd lose out on compiler checks and IDE code hinting if you had to call
>require() directly in AS.
I probably don't know enough about Node and require to understand that.
Let's try looking at source code patterns first. My quick read of require
is
You'd lose out on compiler checks and IDE code hinting if you had to call
require() directly in AS.
Wrapping the generated JS for a class in an IIFE, like I talked about in an
earlier thread, could keep the requires confined to a single class.
(function()
{
var fs = require("fs");
//the f
I read up a bit on Node's require system. It seems that because import
statements in AS are generally at the package level, it wouldn't be a good
equivalent for Node's require. I think Node's require system is an
explicit class/package loader like Java's and allows you to defer the
loading of cod
Node.js has its own require system. It's called CommonJS.
I was thinking that it could also be based on imported classes. It can be a
little tricky, though. A module is pretty flexible with what it exports.
Most simply, a module could export a single class. In this case, the
translation is pretty
On 12/2/15, 9:59 AM, "Josh Tynjala" wrote:
>The require() call for a Node.js module should probably be generated in
>the
>PackageHeaderEmitter, where the goog.require() calls are generated.
OK, but based on what kind of source code lines? The goog.requires are
generated from import statements
The require() call for a Node.js module should probably be generated in the
PackageHeaderEmitter, where the goog.require() calls are generated.
- Josh
On Tue, Dec 1, 2015 at 5:47 PM, Alex Harui wrote:
>
>
> On 12/1/15, 5:06 PM, "Josh Tynjala" wrote:
> >
> >I thought you meant that you were wor
ear it :-)
>
> Thanks,
> Om
>
> On Tue, Dec 1, 2015 at 4:12 PM, Josh Tynjala
> wrote:
>
> > I saw Om mention Node.js support in another thread.
> >
> > On Tue, Dec 1, 2015 at 3:38 PM, OmPrakash Muppirala <
> bigosma...@gmail.com>
> > wrote:
&g
stall flexjs
>> asjac src/HellowWorld.as
>>
>> I have been committing my changes to the feature-npm-install branch of the
>> flex-utilities repo:
>>
>> https://github.com/apache/flex-utilities/tree/feature-npm-install/npm-flexjs
>>
>> Righ
On 12/1/15, 5:06 PM, "Josh Tynjala" wrote:
>
>I thought you meant that you were working on the compiler to add support
>for Node.js modules. Getting the compiler to output good code for running
>on Node.js is something that I hope to work on soon.
>
>For those not familiar, Node.js modules are r
Oh boy, I wish I had started the FlexJS NPM module after you finished your
Node.js support via AS3 :-D
Thanks for the tips. I had it in my TODOs to look at your npm dts2as
utility. I will ping you when I get to the actual compilation of AS3 files
via node part, hopefully soon.
I might need
t; Right now, I am working on getting the Falcon dependencies working (there
> are about a dozen of them)
>
> If there is a better way to do all this, I would love to hear it :-)
>
> Thanks,
> Om
>
> On Tue, Dec 1, 2015 at 4:12 PM, Josh Tynjala
> wrote:
>
> >
Tynjala wrote:
> I saw Om mention Node.js support in another thread.
>
> On Tue, Dec 1, 2015 at 3:38 PM, OmPrakash Muppirala
> wrote:
>
> > Right now, I am working on node.js support for FlexJS.
>
>
> It's something that I'm very interested in, and I planned
I saw Om mention Node.js support in another thread.
On Tue, Dec 1, 2015 at 3:38 PM, OmPrakash Muppirala
wrote:
> Right now, I am working on node.js support for FlexJS.
It's something that I'm very interested in, and I planned to work on this
too, once I found some time. Om, ca
29 matches
Mail list logo
