You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by OK <po...@olafkrueger.net> on 2016/09/07 07:25:59 UTC
Official naming for the "standard" Flex SDK
Hi,
I always stumble over the question what is a clear and unambiguously naming
for the "standard", non "FlexJS" SDK. Cause Apache Flex houses "FlexJS" and
the "standard SDK" a unique naming might be helpful to avoid confusion.
So, is there a naming similar to "FlexJS" and if not, what do you think
about to invent one?
Thanks,
Olaf
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Official-naming-for-the-standard-Flex-SDK-tp54897.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
AW: [Non-DoD Source] Official naming for the "standard" Flex SDK
Posted by Christofer Dutz <ch...@c-ware.de>.
+1 :-) from me :-)
Chris
________________________________
Von: Josh Tynjala <jo...@gmail.com>
Gesendet: Donnerstag, 8. September 2016 16:40:39
An: dev@flex.apache.org
Betreff: Re: [Non-DoD Source] Official naming for the "standard" Flex SDK
You have my agreement too!
- Josh
On Sep 8, 2016 4:15 AM, "Harbs" <ha...@gmail.com> wrote:
> Well, if no one has objections, we can officially agree on it now… ;-)
>
> On Sep 8, 2016, at 11:15 AM, Christofer Dutz <ch...@c-ware.de>
> wrote:
>
> > Hi Harbs,
> >
> >
> > well that's what I'm using when talking about FlexJS, but I couldn't
> remember us actually agreeing on that ;-)
> >
> >
> > Chris
> >
> > ________________________________
> > Von: Harbs <ha...@gmail.com>
> > Gesendet: Donnerstag, 8. September 2016 09:33:44
> > An: dev@flex.apache.org
> > Betreff: Re: [Non-DoD Source] Official naming for the "standard" Flex SDK
> >
> > I think falcon and falconjx can be blurred.
> >
> > I thought we agreed on "FlexJS Compiler" (falcon/falconjx), "FlexJS
> Typedefs” (typedefs) and "FlexJS Framework" (asjs)
> >
> > On Sep 8, 2016, at 1:45 AM, Christofer Dutz <ch...@c-ware.de>
> wrote:
> >
> >> I see it the same way ... Flex and FlexJS is good for me. The only
> thing I was having problems with, was the naming of the inside parts of
> FlexJS: falcon, falconjx, asjs, typedefs ... here I would like some sort of
> consolidation, but not really for Flex/FlexJS.
> >>
> >>
> >> Chris
> >>
> >> ________________________________
> >> Von: OK <po...@olafkrueger.net>
> >> Gesendet: Mittwoch, 7. September 2016 23:58:19
> >> An: dev@flex.apache.org
> >> Betreff: Re: [Non-DoD Source] Re: Official naming for the "standard"
> Flex SDK
> >>
> >> Thanks for your thoughts Marc and Alex.
> >>
> >>> I am hopeful that the "JS" in FlexJS will be enough of a
> differentiator.
> >> FlexJS is definately clear and unambiguously.
> >>
> >> Maybe I was on the wrong track and Apache Flex/Apache FlexJS is
> sufficient.
> >>
> >> Thanks,
> >> Olaf
> >>
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context: http://apache-flex-
> development.2333347.n4.nabble.com/Official-naming-for-the-
> standard-Flex-SDK-tp54897p54938.html
> >> Sent from the Apache Flex Development mailing list archive at
> Nabble.com.
> >
>
>
Re: [Non-DoD Source] Official naming for the "standard" Flex SDK
Posted by Josh Tynjala <jo...@gmail.com>.
You have my agreement too!
- Josh
On Sep 8, 2016 4:15 AM, "Harbs" <ha...@gmail.com> wrote:
> Well, if no one has objections, we can officially agree on it now… ;-)
>
> On Sep 8, 2016, at 11:15 AM, Christofer Dutz <ch...@c-ware.de>
> wrote:
>
> > Hi Harbs,
> >
> >
> > well that's what I'm using when talking about FlexJS, but I couldn't
> remember us actually agreeing on that ;-)
> >
> >
> > Chris
> >
> > ________________________________
> > Von: Harbs <ha...@gmail.com>
> > Gesendet: Donnerstag, 8. September 2016 09:33:44
> > An: dev@flex.apache.org
> > Betreff: Re: [Non-DoD Source] Official naming for the "standard" Flex SDK
> >
> > I think falcon and falconjx can be blurred.
> >
> > I thought we agreed on "FlexJS Compiler" (falcon/falconjx), "FlexJS
> Typedefs” (typedefs) and "FlexJS Framework" (asjs)
> >
> > On Sep 8, 2016, at 1:45 AM, Christofer Dutz <ch...@c-ware.de>
> wrote:
> >
> >> I see it the same way ... Flex and FlexJS is good for me. The only
> thing I was having problems with, was the naming of the inside parts of
> FlexJS: falcon, falconjx, asjs, typedefs ... here I would like some sort of
> consolidation, but not really for Flex/FlexJS.
> >>
> >>
> >> Chris
> >>
> >> ________________________________
> >> Von: OK <po...@olafkrueger.net>
> >> Gesendet: Mittwoch, 7. September 2016 23:58:19
> >> An: dev@flex.apache.org
> >> Betreff: Re: [Non-DoD Source] Re: Official naming for the "standard"
> Flex SDK
> >>
> >> Thanks for your thoughts Marc and Alex.
> >>
> >>> I am hopeful that the "JS" in FlexJS will be enough of a
> differentiator.
> >> FlexJS is definately clear and unambiguously.
> >>
> >> Maybe I was on the wrong track and Apache Flex/Apache FlexJS is
> sufficient.
> >>
> >> Thanks,
> >> Olaf
> >>
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context: http://apache-flex-
> development.2333347.n4.nabble.com/Official-naming-for-the-
> standard-Flex-SDK-tp54897p54938.html
> >> Sent from the Apache Flex Development mailing list archive at
> Nabble.com.
> >
>
>
Re: [Non-DoD Source] Official naming for the "standard" Flex SDK
Posted by Harbs <ha...@gmail.com>.
Well, if no one has objections, we can officially agree on it now… ;-)
On Sep 8, 2016, at 11:15 AM, Christofer Dutz <ch...@c-ware.de> wrote:
> Hi Harbs,
>
>
> well that's what I'm using when talking about FlexJS, but I couldn't remember us actually agreeing on that ;-)
>
>
> Chris
>
> ________________________________
> Von: Harbs <ha...@gmail.com>
> Gesendet: Donnerstag, 8. September 2016 09:33:44
> An: dev@flex.apache.org
> Betreff: Re: [Non-DoD Source] Official naming for the "standard" Flex SDK
>
> I think falcon and falconjx can be blurred.
>
> I thought we agreed on "FlexJS Compiler" (falcon/falconjx), "FlexJS Typedefs” (typedefs) and "FlexJS Framework" (asjs)
>
> On Sep 8, 2016, at 1:45 AM, Christofer Dutz <ch...@c-ware.de> wrote:
>
>> I see it the same way ... Flex and FlexJS is good for me. The only thing I was having problems with, was the naming of the inside parts of FlexJS: falcon, falconjx, asjs, typedefs ... here I would like some sort of consolidation, but not really for Flex/FlexJS.
>>
>>
>> Chris
>>
>> ________________________________
>> Von: OK <po...@olafkrueger.net>
>> Gesendet: Mittwoch, 7. September 2016 23:58:19
>> An: dev@flex.apache.org
>> Betreff: Re: [Non-DoD Source] Re: Official naming for the "standard" Flex SDK
>>
>> Thanks for your thoughts Marc and Alex.
>>
>>> I am hopeful that the "JS" in FlexJS will be enough of a differentiator.
>> FlexJS is definately clear and unambiguously.
>>
>> Maybe I was on the wrong track and Apache Flex/Apache FlexJS is sufficient.
>>
>> Thanks,
>> Olaf
>>
>>
>>
>>
>>
>> --
>> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Official-naming-for-the-standard-Flex-SDK-tp54897p54938.html
>> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
AW: [Non-DoD Source] Official naming for the "standard" Flex SDK
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Harbs,
well that's what I'm using when talking about FlexJS, but I couldn't remember us actually agreeing on that ;-)
Chris
________________________________
Von: Harbs <ha...@gmail.com>
Gesendet: Donnerstag, 8. September 2016 09:33:44
An: dev@flex.apache.org
Betreff: Re: [Non-DoD Source] Official naming for the "standard" Flex SDK
I think falcon and falconjx can be blurred.
I thought we agreed on "FlexJS Compiler" (falcon/falconjx), "FlexJS Typedefs” (typedefs) and "FlexJS Framework" (asjs)
On Sep 8, 2016, at 1:45 AM, Christofer Dutz <ch...@c-ware.de> wrote:
> I see it the same way ... Flex and FlexJS is good for me. The only thing I was having problems with, was the naming of the inside parts of FlexJS: falcon, falconjx, asjs, typedefs ... here I would like some sort of consolidation, but not really for Flex/FlexJS.
>
>
> Chris
>
> ________________________________
> Von: OK <po...@olafkrueger.net>
> Gesendet: Mittwoch, 7. September 2016 23:58:19
> An: dev@flex.apache.org
> Betreff: Re: [Non-DoD Source] Re: Official naming for the "standard" Flex SDK
>
> Thanks for your thoughts Marc and Alex.
>
>> I am hopeful that the "JS" in FlexJS will be enough of a differentiator.
> FlexJS is definately clear and unambiguously.
>
> Maybe I was on the wrong track and Apache Flex/Apache FlexJS is sufficient.
>
> Thanks,
> Olaf
>
>
>
>
>
> --
> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Official-naming-for-the-standard-Flex-SDK-tp54897p54938.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [Non-DoD Source] Official naming for the "standard" Flex SDK
Posted by Harbs <ha...@gmail.com>.
I think falcon and falconjx can be blurred.
I thought we agreed on "FlexJS Compiler" (falcon/falconjx), "FlexJS Typedefs” (typedefs) and "FlexJS Framework" (asjs)
On Sep 8, 2016, at 1:45 AM, Christofer Dutz <ch...@c-ware.de> wrote:
> I see it the same way ... Flex and FlexJS is good for me. The only thing I was having problems with, was the naming of the inside parts of FlexJS: falcon, falconjx, asjs, typedefs ... here I would like some sort of consolidation, but not really for Flex/FlexJS.
>
>
> Chris
>
> ________________________________
> Von: OK <po...@olafkrueger.net>
> Gesendet: Mittwoch, 7. September 2016 23:58:19
> An: dev@flex.apache.org
> Betreff: Re: [Non-DoD Source] Re: Official naming for the "standard" Flex SDK
>
> Thanks for your thoughts Marc and Alex.
>
>> I am hopeful that the "JS" in FlexJS will be enough of a differentiator.
> FlexJS is definately clear and unambiguously.
>
> Maybe I was on the wrong track and Apache Flex/Apache FlexJS is sufficient.
>
> Thanks,
> Olaf
>
>
>
>
>
> --
> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Official-naming-for-the-standard-Flex-SDK-tp54897p54938.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
AW: [Non-DoD Source] Re: Official naming for the "standard" Flex SDK
Posted by Christofer Dutz <ch...@c-ware.de>.
I see it the same way ... Flex and FlexJS is good for me. The only thing I was having problems with, was the naming of the inside parts of FlexJS: falcon, falconjx, asjs, typedefs ... here I would like some sort of consolidation, but not really for Flex/FlexJS.
Chris
________________________________
Von: OK <po...@olafkrueger.net>
Gesendet: Mittwoch, 7. September 2016 23:58:19
An: dev@flex.apache.org
Betreff: Re: [Non-DoD Source] Re: Official naming for the "standard" Flex SDK
Thanks for your thoughts Marc and Alex.
>I am hopeful that the "JS" in FlexJS will be enough of a differentiator.
FlexJS is definately clear and unambiguously.
Maybe I was on the wrong track and Apache Flex/Apache FlexJS is sufficient.
Thanks,
Olaf
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Official-naming-for-the-standard-Flex-SDK-tp54897p54938.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [Non-DoD Source] Re: Official naming for the "standard" Flex
SDK
Posted by OK <po...@olafkrueger.net>.
Thanks for your thoughts Marc and Alex.
>I am hopeful that the "JS" in FlexJS will be enough of a differentiator.
FlexJS is definately clear and unambiguously.
Maybe I was on the wrong track and Apache Flex/Apache FlexJS is sufficient.
Thanks,
Olaf
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Official-naming-for-the-standard-Flex-SDK-tp54897p54938.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [Non-DoD Source] Re: Official naming for the "standard" Flex SDK
Posted by Alex Harui <ah...@adobe.com>.
On 9/7/16, 3:56 AM, "OK" <po...@olafkrueger.net> wrote:
>Kessler CTR Mark J wrote
>> Should not use flash in the name. The main SDK can target flash player,
>> air, and native apps (with captive runtime).
>
>Hmm, I thought that all these runtimes are under the same hood wich is
>called "Flash platform" by Adobe.
>Seems that the Adobe naming confused me also ;-)
Well you do need tools from the Adobe Flash team to target the native apps.
I agree that there is a possibility that better naming could reduce
confusion, but I also agree with Mark that renaming the current Flex SDK
as "Flex Flash Platform" wouldn't be my first choice.
>
>
>Kessler CTR Mark J wrote
>> Then there is FlexJS which is divergent from the main SDK. So I think
>> Apache Flex as a title would do just fine.
>
>Ok, but that means that both SDKs exists side by side:
>->Apache Flex
>->Apache FlexJS
>
>But my understanding is that FlexJS is under the hood of Apache Flex:
>->Apache Flex
>-->FlexJS
>-->Previous Flex
Not sure what you mean by under-the-hood. Sure, Apache Flex is the
project name, but for product names, I think we do want the Apache FlexJS
SDK to be just another option along with the Apache Flex SDK. I am
hopeful that the "JS" in FlexJS will be enough of a differentiator. I've
tried to avoid using "legacy" when referencing the current Flex SDK.
Longer term, what if someone writes a TypeScript emitter for FalconJX? I
think we'd still put it under the FlexJS moniker and not start using the
term FlexTS, but I could be convinced otherwise.
My 2 cents,
-Alex
RE: [Non-DoD Source] Re: Official naming for the "standard" Flex
SDK
Posted by OK <po...@olafkrueger.net>.
Kessler CTR Mark J wrote
> Should not use flash in the name. The main SDK can target flash player,
> air, and native apps (with captive runtime).
Hmm, I thought that all these runtimes are under the same hood wich is
called "Flash platform" by Adobe.
Seems that the Adobe naming confused me also ;-)
Kessler CTR Mark J wrote
> Then there is FlexJS which is divergent from the main SDK. So I think
> Apache Flex as a title would do just fine.
Ok, but that means that both SDKs exists side by side:
->Apache Flex
->Apache FlexJS
But my understanding is that FlexJS is under the hood of Apache Flex:
->Apache Flex
-->FlexJS
-->Previous Flex
So if you'd like to make sure that there will be no confusion if you talk or
write just about "Apache Flex" you have to mention that you mean the "AIR,
Flash,... whatever SDK".
Probably at the end this discussion is useless but maybe a unique name would
avoid confusion, especially if FlexJS gets more and more popular and moves
into the focus of non-Flex developers.
Thanks,
Olaf
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Official-naming-for-the-standard-Flex-SDK-tp54897p54911.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: [Non-DoD Source] Re: Official naming for the "standard" Flex SDK
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
Should not use flash in the name. The main SDK can target flash player, air, and native apps (with captive runtime). Then there is FlexJS which is divergent from the main SDK. So I think Apache Flex as a title would do just fine.
-Mark
-----Original Message-----
From: OK [mailto:post@olafkrueger.net]
Sent: Wednesday, September 07, 2016 3:39 AM
To: dev@flex.apache.org
Subject: [Non-DoD Source] Re: Official naming for the "standard" Flex SDK
Forgot to mention my proposal:
FlexJS -> Flex JavaScript
FlexFP -> Flex Flash Platform
Thanks,
Olaf
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Official-naming-for-the-standard-Flex-SDK-tp54897p54898.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: Official naming for the "standard" Flex SDK
Posted by OK <po...@olafkrueger.net>.
Forgot to mention my proposal:
FlexJS -> Flex JavaScript
FlexFP -> Flex Flash Platform
Thanks,
Olaf
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Official-naming-for-the-standard-Flex-SDK-tp54897p54898.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.