Good page, Harbs. We should move it under the FlexJS tree somewhere.
I have no objections to changing "externs" to something else.
One nit: it says externs are "linked at compile-time". Might be better to
say, "used for type-checking at compile-time".
Thanks,
-Alex
+1 for the renaming to typedefs or anything but "externs"
Chris
Von: Harbs
Gesendet: Sonntag, 8. Mai 2016 18:35:36
An: dev@flex.apache.org
Betreff: Re: FlexJS identity crisis. was: [Discuss]Accept donation of drawing
APIs
FWIW, I was reflecting on the n
Hi Harbs,
thanks for writing and drawing this up. It exactly matches my impression and it
exactly matches the naming convention I used for the Mavenization as I used the
following group Ids:
org.apache.flex.flexjs.compiler
org.apache.flex.flexjs.framewort
org.apache.flex.flexjs.extern
I too th
On 4/23/16, 2:12 AM, "Christofer Dutz" wrote:
>Hi Alex ...
>
>first ... the official name should probably even contain the "Apache
>Flex" so I guess the correct name would probably be "Apache Flex FlexJS
>Compiler"
We are trying to establish FlexJS and Apache FlexJS as trademarks, so I
don't
Von: Alex Harui
Gesendet: Freitag, 22. April 2016 20:40
An: dev@flex.apache.org
Betreff: Re: AW: FlexJS identity crisis. was: [Discuss]Accept donation of
drawing APIs
On 4/21/16, 1:27 PM, "Christofer Dutz" wrote:
>When creating maven artifacts from SDKs we had a differen
What about simply naming the compiler "FlexJS Compiler"? Currently the maven
plugin for example has a reference to falcon.jx and falcon and selects the
right compc version using the Flex Tool Group API. So having different variants
inside the compiler package doesn't seem too confusing.
Anyway
Yeah, long file names like that are very unappealing. We need to try to
avoid that situation.
- Josh
On Apr 22, 2016 11:40 AM, "Alex Harui" wrote:
>
>
> On 4/21/16, 1:27 PM, "Christofer Dutz" wrote:
>
> >When creating maven artifacts from SDKs we had a different naming, which
> >I find a little
On 4/21/16, 1:27 PM, "Christofer Dutz" wrote:
>When creating maven artifacts from SDKs we had a different naming, which
>I find a little more intuitive.
>Applied to FlexJS instead of Flex, this would be:
>
>FlexJS Compiler: Falcon, FalconJX
>FlexJS Framework: ASJS
>FlexJS Externs: Externs
>
>Ho
When creating maven artifacts from SDKs we had a different naming, which I find
a little more intuitive.
Applied to FlexJS instead of Flex, this would be:
FlexJS Compiler: Falcon, FalconJX
FlexJS Framework: ASJS
FlexJS Externs: Externs
How about this .. but I agree in the part where you call cal
Sounds like that ASP 5... wait I mean ASP Core v1.0.
-Mark
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Wednesday, April 20, 2016 12:47 PM
To: dev@flex.apache.org
Subject: [Non-DoD Source] Re: AW: FlexJS identity crisis. was: [Discuss]Accept
donation of drawing
On 4/20/16, 7:16 AM, "Christofer Dutz" wrote:
>And what about calling that stuff "Flex 5"?
>
>We'd have the flex5 compiler (aka Falcon), framework (aka ASJS) ...
Possible, but IMO, Flex 5 implies more backward-compatibility than FlexJS
can currently deliver.
That said, as I've been working on
And what about calling that stuff "Flex 5"?
We'd have the flex5 compiler (aka Falcon), framework (aka ASJS) ...
Chris
Von: Alex Harui
Gesendet: Mittwoch, 20. April 2016 07:02
An: dev@flex.apache.org
Betreff: Re: FlexJS identity crisis. was: [Discuss]Acce
12 matches
Mail list logo
