Re: [DISCUSS] Name of the FlexJS Fork

[Dave Fisher]

Hi Carlos.

> On Sep 12, 2017, at 5:39 AM, Carlos Rovira  
> wrote:
> 
> Hi, just see this now, but I responded in the other thread. copying
> response:
> 
> Regarding name, I would prefer a name change since the suffix "JS" is not
> reflecting the real potential of this project. If we want to output JS
> exclusively, I think it would be ok.
> 
> In the other hand, "Flex" name has very bad press in IT and companies. If
> you put the word "Flex", you can have many problems with your work and
> credibility with the people you talk.

Do you have examples of Apache Flex or FlexJS getting bad press? It would make 
your argument more persuasive.

> 
> In the other hand, we should look at our competitors : Angular, React, Vue,
> Dart,... it's all marketing: the name, the website, if we don't play well
> our cards, don't expect to have a widely used technology

You mean like Beads, Bend or Strands?

> 
> In the other hand I can live with old "FlexJS" name, if people does not
> want a change, but these means to me that FlexJS will hardly get considered
> in the mainstream.
> 
> Just my 2

More than that ;-)

Regards,
Dave

> 
> thanks
> 
> Carlos
> 
> 
> 
> 2017-09-12 10:58 GMT+02:00 Harbs :
> 
>> I personally do not see a need for a new name.
>> 
>> To me it’s more about branding the name. If FlexJS has its own identity
>> and Flash is barely mentioned I don’t think it’s dragging along the Flash
>> associations. For those familiar with Flex and wanting to migrate to JS,
>> the FlexJS name is a positive thing.
>> 
>> Harbs
>> 
>>> On Sep 12, 2017, at 4:01 AM, Dave Fisher  wrote:
>>> 
>>> Hi -
>>> 
>>> In discussions on the Board and Private list about the proposal voted on
>> a few weeks ago to fork FlexJS it was pointed out that it would good to
>> discuss if a new name should be attached to the forked project.
>>> 
>>> There are one or two propositions to discuss.
>>> 
>>> (1) FlexJS - is this distinct enough and will the historical connection
>> to Adobe/Apache Flex and Flash help or hinder the forked project’s future?
>>> 
>>> Please provide arguments in any direction.
>>> 
>>> (2) If a change is the outcome then we need to discuss and accumulate
>> reasonable names. Determine what is suitable by checking for other uses of
>> these names. If there are multiple choices available then we should vote.
>>> 
>>> A discussion of possible names can go in parallel to the discussion
>> about keeping FlexJS.
>>> 
>>> This discussion needs to proceed quickly if we want to have an open
>> process in advance of the next ASF Board meeting.
>>> 
>>> Regards,
>>> Dave
>> 
>> 
> 
> 
> --
> 
> 
> 
> Carlos Rovira
> 
> Director General
> 
> M: +34 607 22 60 05
> 
> http://www.codeoscopic.com
> 
> http://www.avant2.es
> 
> 
> Conocenos en 1 minuto! 
> 
> 
> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> información privilegiada o confidencial. Si ha recibido este mensaje por
> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> proceda a su destrucción.
> 
> De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
> que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> servicio o información solicitados, teniendo usted derecho de acceso,
> rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
> necesaria.



signature.asc
Description: Message signed with OpenPGP

RE: [DISCUSS] Name of the FlexJS Fork

[Chris Martin]

Hey team,

I feel that FlexJS is the right name for the same reasons mentioned by other 
team members thus far.

Key one is that we’ve got the next 3 years to capitalize on the “Flex” name for 
users to see a possible migration path. I feel that keeping this name will make 
it easier for Developers who are being asked to migrate an Apache Flex web app 
to find our project.

Chris

Sent from Mail for Windows 10

From: Dave Fisher
Sent: Tuesday, September 12, 2017 8:03 AM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Name of the FlexJS Fork

Hi -

I specifically asked Shane about when a trademark becomes an Apache mark. The 
answer can be summarized as once it is used. For a project that is when it 
approved and the website goes up. For a product it is when it is released. The 
TM ought be used to make it clear, but it can be implicit. It is important to 
do the Suitable Name Search to make sure that it looks like use of a name would 
not infringe on someone else’s mark.

> On Sep 11, 2017, at 11:20 PM, Alex Harui  wrote:
>
> I would like some thoughts on a related question, but first some context:
>
> IMO, it would help to continue to develop and ship a product called Apache
> FlexJS right now to draw in migrating Flex folks.  And maybe some day,
> we'll ship a product that is more targeted to folks writing new JS apps
> and maybe even target runtimes other than JS, and that might have a name
> that doesn't have Flex in it.  So, the _project_ could be called something
> else, but it seems odd for there to be an Apache Flex project and an
> Apache XX project that ships an Apache FlexJS product.

Assuming Flex will allow XX to do so yes.

>
> So my question is: How impactful the project name is compared to the
> product name?  I'm not sure I can recite the project/manufacturer names
> behind many products but most are the same at Apache.

Around Lucene which came out of Nutch:
Apache Lucene is a project and product. Apache Solr is a product of Apache 
Lucene.
Apache Lucene.Net is a project and product.
Apache Lucy is a project and product.

>
> So, if someone thinks of a great project name that can encompass these
> possibilities in our future and Apache authorities won't object to using
> FlexJS for a product in a project with a different name, I would be in
> favor of the new name, but if project names aren't as impactful as product
> names, I'd just lean towards sticking with FlexJS as the project name for
> now just so we can get the proposal decided on in the September 20 board
> meeting and not have to wait more.

If we think a new name is appropriate then now is the time that’s why we should 
move ahead.

Regards,
Dave

>
> Thoughts?
> -Alex
>
> On 9/11/17, 9:35 PM, "Piotr Zarzycki"  wrote:
>
>> Hi Dave,
>>
>> I believe that FlexJS is the right name. We have gained some recognition
>> and visibility among people and companies. I don't believe that we are
>> really at the beginning anymore.
>>
>> Our main first customers are companies who would like to rewrite their
>> apps
>> from Flex, so this connection is something really good.
>> If majority which response to this thread would like to change the name I
>> will not fight. Keep in mind that we really would like to have the project
>> split - I believe that is the most important to us.
>>
>> Thanks,
>> Piotr
>>
>> 2017-09-12 3:01 GMT+02:00 Dave Fisher :
>>
>>> Hi -
>>>
>>> In discussions on the Board and Private list about the proposal voted
>>> on a
>>> few weeks ago to fork FlexJS it was pointed out that it would good to
>>> discuss if a new name should be attached to the forked project.
>>>
>>> There are one or two propositions to discuss.
>>>
>>> (1) FlexJS - is this distinct enough and will the historical connection
>>> to
>>> Adobe/Apache Flex and Flash help or hinder the forked project’s future?
>>>
>>> Please provide arguments in any direction.
>>>
>>> (2) If a change is the outcome then we need to discuss and accumulate
>>> reasonable names. Determine what is suitable by checking for other uses
>>> of
>>> these names. If there are multiple choices available then we should
>>> vote.
>>>
>>> A discussion of possible names can go in parallel to the discussion
>>> about
>>> keeping FlexJS.
>>>
>>> This discussion needs to proceed quickly if we want to have an open
>>> process in advance of the next ASF Board meeting.
>>>
>>> Regards,
>>> Dave
>>>
>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> mobile: +48 880 859 557 <+48%20880%20859%20557>
>> skype: zarzycki10
>>
>> LinkedIn:
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linked
>> in.com%2Fpiotrzarzycki=02%7C01%7C%7C9e4bacb6b08a4923de8108d4f997b9a7%
>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636407877434499520=Nhht
>> Kaf9RlzE9cCdJ3WErVGfHVFXsdQX%2BK48hw0Der8%3D=0
>> 

Re: [FLEX JS] How to import mx.managers.PopUpManager?

[Alex Harui]

FWIW, the reason there is no PopUpManager in FlexJS is only because nobody
has needed it yet.  The mx.managers.PopUpManager and related classes is a
pretty sophisticated subsystem that allows multiple "top-level"
overlapping windows.  All of that code is only truly needed if you have
more than one popup on the screen at a time and folks need to move them
around and overlap them.

FlexJS is being implemented with a pay-as-you-go (PAYG) philosophy.  So
far, all of our code only needs to popup one thing at a time, so you can
just find an IPopUpHost or use the main view and call addElement and
removeElement and you app will be smaller and faster.

But if you do need overlapping top-level windows, then we need a volunteer
to create the equivalent functionality for FlexJS.

Thanks,
-Alex

On 9/12/17, 4:50 AM, "Piotr Zarzycki"  wrote:

>Exactly!
>
>It is in general means that if you have clean up ActionScript logic(no
>Flash dependency) in your old application - you can in most cases take it
>and use it in your FlexJS code, with some correction like usage of
>ArrayCollection:)
>
>Thanks,
>Piotr
>
>
>2017-09-12 13:42 GMT+02:00 Olaf Krueger :
>
>> m_awais wrote
>> > I am trying to import mx.managers.PopUpManager in my flex JS project
>>mxml
>> > file.
>>
>> There's no way to use "s:" or "mx:" components with FlexJS!
>> In general, you can't reuse anything that has a dependency to Flash or
>> classic Flex!
>> This is also true for e.g. the "mx.collections.ArrayCollection".
>>
>> HTH,
>> Olaf
>>
>>
>>
>>
>> --
>> Sent from: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl
>>ex-development.247.n4.nabble.com%2F=02%7C01%7C%7C337c7a12abdb423
>>4f87a08d4f9d47424%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364081382
>>59812516=oY7lrbk9Z9ElyK2z0G7jJQoC6%2B82wiBA8YUAv%2FZzjJQ%3D
>>d=0
>>
>
>
>
>-- 
>
>Piotr Zarzycki
>
>mobile: +48 880 859 557
>skype: zarzycki10
>
>LinkedIn: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linked
>in.com%2Fpiotrzarzycki=02%7C01%7C%7C337c7a12abdb4234f87a08d4f9d47424%
>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636408138259812516=re0Y
>Mxv2SvdGqPrv5fEkZaV53pIqdYHmakDypQG09p8%3D=0
>din.com%2Fin%2Fpiotr-zarzycki-92a53552=02%7C01%7C%7C337c7a12abdb4234f
>87a08d4f9d47424%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364081382598
>12516=zoyGfdFzqmbbIxJq%2BvdB034ZV6GPXyCYrxus8qOmJzI%3D=0>

Re: [FlexJS, AMF] Steps to make FlexJS / Java - RemoteObject / AMF sample work

[Alex Harui]

Hi Prashant,

Are you testing with the example code or your own app.  I see MainView in
the stack trace and there isn't one in the example.  If you have your own
code, make sure ClassAliasBead is a bead on the Application and not the
View.

Thanks,
-Alex

On 9/12/17, 3:59 AM, "PKumar"  wrote:

>I downloaded the  latest nightly build and used that. I am also compiled
>this
>app with the FlexJS package  that you shared. but same error i am
>getting.
>
>
>
>--
>Sent from: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2F=02%7C01%7C%7C489a01ccda8743389
>c8108d4f9cd67f2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364081079906
>70935=yxNQrjQGUZ45dajNkA%2F8h8eMW1kbG4%2BmldxbtcVwzg0%3D=0

Re: [DISCUSS] Name of the FlexJS Fork

[Dave Fisher]

Hi -

I specifically asked Shane about when a trademark becomes an Apache mark. The 
answer can be summarized as once it is used. For a project that is when it 
approved and the website goes up. For a product it is when it is released. The 
TM ought be used to make it clear, but it can be implicit. It is important to 
do the Suitable Name Search to make sure that it looks like use of a name would 
not infringe on someone else’s mark.

> On Sep 11, 2017, at 11:20 PM, Alex Harui  wrote:
> 
> I would like some thoughts on a related question, but first some context:
> 
> IMO, it would help to continue to develop and ship a product called Apache
> FlexJS right now to draw in migrating Flex folks.  And maybe some day,
> we'll ship a product that is more targeted to folks writing new JS apps
> and maybe even target runtimes other than JS, and that might have a name
> that doesn't have Flex in it.  So, the _project_ could be called something
> else, but it seems odd for there to be an Apache Flex project and an
> Apache XX project that ships an Apache FlexJS product.

Assuming Flex will allow XX to do so yes.

> 
> So my question is: How impactful the project name is compared to the
> product name?  I'm not sure I can recite the project/manufacturer names
> behind many products but most are the same at Apache.

Around Lucene which came out of Nutch:
Apache Lucene is a project and product. Apache Solr is a product of Apache 
Lucene.
Apache Lucene.Net is a project and product.
Apache Lucy is a project and product.

> 
> So, if someone thinks of a great project name that can encompass these
> possibilities in our future and Apache authorities won't object to using
> FlexJS for a product in a project with a different name, I would be in
> favor of the new name, but if project names aren't as impactful as product
> names, I'd just lean towards sticking with FlexJS as the project name for
> now just so we can get the proposal decided on in the September 20 board
> meeting and not have to wait more.

If we think a new name is appropriate then now is the time that’s why we should 
move ahead.

Regards,
Dave

> 
> Thoughts?
> -Alex
> 
> On 9/11/17, 9:35 PM, "Piotr Zarzycki"  wrote:
> 
>> Hi Dave,
>> 
>> I believe that FlexJS is the right name. We have gained some recognition
>> and visibility among people and companies. I don't believe that we are
>> really at the beginning anymore.
>> 
>> Our main first customers are companies who would like to rewrite their
>> apps
>> from Flex, so this connection is something really good.
>> If majority which response to this thread would like to change the name I
>> will not fight. Keep in mind that we really would like to have the project
>> split - I believe that is the most important to us.
>> 
>> Thanks,
>> Piotr
>> 
>> 2017-09-12 3:01 GMT+02:00 Dave Fisher :
>> 
>>> Hi -
>>> 
>>> In discussions on the Board and Private list about the proposal voted
>>> on a
>>> few weeks ago to fork FlexJS it was pointed out that it would good to
>>> discuss if a new name should be attached to the forked project.
>>> 
>>> There are one or two propositions to discuss.
>>> 
>>> (1) FlexJS - is this distinct enough and will the historical connection
>>> to
>>> Adobe/Apache Flex and Flash help or hinder the forked project’s future?
>>> 
>>> Please provide arguments in any direction.
>>> 
>>> (2) If a change is the outcome then we need to discuss and accumulate
>>> reasonable names. Determine what is suitable by checking for other uses
>>> of
>>> these names. If there are multiple choices available then we should
>>> vote.
>>> 
>>> A discussion of possible names can go in parallel to the discussion
>>> about
>>> keeping FlexJS.
>>> 
>>> This discussion needs to proceed quickly if we want to have an open
>>> process in advance of the next ASF Board meeting.
>>> 
>>> Regards,
>>> Dave
>>> 
>> 
>> 
>> 
>> --
>> 
>> Piotr Zarzycki
>> 
>> mobile: +48 880 859 557 <+48%20880%20859%20557>
>> skype: zarzycki10
>> 
>> LinkedIn:
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linked
>> in.com%2Fpiotrzarzycki=02%7C01%7C%7C9e4bacb6b08a4923de8108d4f997b9a7%
>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636407877434499520=Nhht
>> Kaf9RlzE9cCdJ3WErVGfHVFXsdQX%2BK48hw0Der8%3D=0
>> > din.com%2Fin%2Fpiotr-zarzycki-92a53552=02%7C01%7C%7C9e4bacb6b08a4923d
>> e8108d4f997b9a7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364078774344
>> 99520=el1sClOn82J2rnnm4N01Te8Z5bPylMriHy%2Fdp0%2Budd0%3D=0>
> 



signature.asc
Description: Message signed with OpenPGP

Re: [FLEX JS] How to import mx.managers.PopUpManager?

[m_awais]

Thank you all for reply.

pkumar thanks for the link. I tried to use the imports from that link. My
application gives error on

"import views.PopUpView" and states : Definition views.PopUpView could'nt be
found.

Also it showing "xmlns:ns1" keywords in red. I verified the path is correct.

Any ideas?

Thanks!



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [DISCUSS] Name of the FlexJS Fork

[Carlos Rovira]

Hi, just see this now, but I responded in the other thread. copying
response:

Regarding name, I would prefer a name change since the suffix "JS" is not
reflecting the real potential of this project. If we want to output JS
exclusively, I think it would be ok.

In the other hand, "Flex" name has very bad press in IT and companies. If
you put the word "Flex", you can have many problems with your work and
credibility with the people you talk.

In the other hand, we should look at our competitors : Angular, React, Vue,
Dart,... it's all marketing: the name, the website, if we don't play well
our cards, don't expect to have a widely used technology

In the other hand I can live with old "FlexJS" name, if people does not
want a change, but these means to me that FlexJS will hardly get considered
in the mainstream.

Just my 2

thanks

Carlos



2017-09-12 10:58 GMT+02:00 Harbs :

> I personally do not see a need for a new name.
>
> To me it’s more about branding the name. If FlexJS has its own identity
> and Flash is barely mentioned I don’t think it’s dragging along the Flash
> associations. For those familiar with Flex and wanting to migrate to JS,
> the FlexJS name is a positive thing.
>
> Harbs
>
> > On Sep 12, 2017, at 4:01 AM, Dave Fisher  wrote:
> >
> > Hi -
> >
> > In discussions on the Board and Private list about the proposal voted on
> a few weeks ago to fork FlexJS it was pointed out that it would good to
> discuss if a new name should be attached to the forked project.
> >
> > There are one or two propositions to discuss.
> >
> > (1) FlexJS - is this distinct enough and will the historical connection
> to Adobe/Apache Flex and Flash help or hinder the forked project’s future?
> >
> > Please provide arguments in any direction.
> >
> > (2) If a change is the outcome then we need to discuss and accumulate
> reasonable names. Determine what is suitable by checking for other uses of
> these names. If there are multiple choices available then we should vote.
> >
> > A discussion of possible names can go in parallel to the discussion
> about keeping FlexJS.
> >
> > This discussion needs to proceed quickly if we want to have an open
> process in advance of the next ASF Board meeting.
> >
> > Regards,
> > Dave
>
>


-- 



Carlos Rovira

Director General

M: +34 607 22 60 05

http://www.codeoscopic.com

http://www.avant2.es


Conocenos en 1 minuto! 


Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.

Re: [FLEX JS] How to import mx.managers.PopUpManager?

[PKumar]

check the  sample code at following github link

https://github.com/pkumar-ghub/ApacheFlexJSDemo/tree/master/PopupWindow



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [FLEX JS] How to import mx.managers.PopUpManager?

[Piotr Zarzycki]

Exactly!

It is in general means that if you have clean up ActionScript logic(no
Flash dependency) in your old application - you can in most cases take it
and use it in your FlexJS code, with some correction like usage of
ArrayCollection:)

Thanks,
Piotr


2017-09-12 13:42 GMT+02:00 Olaf Krueger :

> m_awais wrote
> > I am trying to import mx.managers.PopUpManager in my flex JS project mxml
> > file.
>
> There's no way to use "s:" or "mx:" components with FlexJS!
> In general, you can't reuse anything that has a dependency to Flash or
> classic Flex!
> This is also true for e.g. the "mx.collections.ArrayCollection".
>
> HTH,
> Olaf
>
>
>
>
> --
> Sent from: http://apache-flex-development.247.n4.nabble.com/
>



-- 

Piotr Zarzycki

mobile: +48 880 859 557
skype: zarzycki10

LinkedIn: http://www.linkedin.com/piotrzarzycki

Re: [FLEX JS] How to import mx.managers.PopUpManager?

[Olaf Krueger]

m_awais wrote
> I am trying to import mx.managers.PopUpManager in my flex JS project mxml
> file.

There's no way to use "s:" or "mx:" components with FlexJS!
In general, you can't reuse anything that has a dependency to Flash or
classic Flex!
This is also true for e.g. the "mx.collections.ArrayCollection".

HTH,
Olaf




--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [FLEX JS] How to import mx.managers.PopUpManager?

[Piotr Zarzycki]

Hi Muhammad,

You cannot simply import something from old Flex. UI creation in FlexJS is
very different.
There is util [1] which you can mainly use I think similar as PopUpManager,
but I have to admit I didn't explore yet this one.

[1]
https://github.com/apache/flex-asjs/blob/develop/frameworks/projects/Core/src/main/flex/org/apache/flex/utils/UIUtils.as

Thanks,
Piotr


2017-09-12 13:06 GMT+02:00 m_awais :

> Hi,
>
> I am trying to import mx.managers.PopUpManager in my flex JS project mxml
> file. I tried different import statements but none of them worked.
>
> xmlns:mx="library://ns.apache.org/flex/mx"  in  tag
>
> import org.apache.flex.mx.managers.PopUpManager; in  tag
>
> Is there anything additional i am missing, or my import syntax is wrong?
>
> Thanks!
>
>
>
>
>
>
> --
> Sent from: http://apache-flex-development.247.n4.nabble.com/
>



-- 

Piotr Zarzycki

mobile: +48 880 859 557
skype: zarzycki10

LinkedIn: http://www.linkedin.com/piotrzarzycki

[FLEX JS] How to import mx.managers.PopUpManager?

[m_awais]

Hi,

I am trying to import mx.managers.PopUpManager in my flex JS project mxml
file. I tried different import statements but none of them worked.

xmlns:mx="library://ns.apache.org/flex/mx"  in  tag

import org.apache.flex.mx.managers.PopUpManager; in  tag

Is there anything additional i am missing, or my import syntax is wrong?

Thanks!






--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [FlexJS, AMF] Steps to make FlexJS / Java - RemoteObject / AMF sample work

[PKumar]

I downloaded the  latest nightly build and used that. I am also compiled this
app with the FlexJS package  that you shared. but same error i am  getting.



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [Flex JS] Adobe substitute

[m_awais]

Thank you All for help.

Regards



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [DISCUSS] Name of the FlexJS Fork

[Harbs]

I personally do not see a need for a new name.

To me it’s more about branding the name. If FlexJS has its own identity and 
Flash is barely mentioned I don’t think it’s dragging along the Flash 
associations. For those familiar with Flex and wanting to migrate to JS, the 
FlexJS name is a positive thing.

Harbs

> On Sep 12, 2017, at 4:01 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> In discussions on the Board and Private list about the proposal voted on a 
> few weeks ago to fork FlexJS it was pointed out that it would good to discuss 
> if a new name should be attached to the forked project.
> 
> There are one or two propositions to discuss.
> 
> (1) FlexJS - is this distinct enough and will the historical connection to 
> Adobe/Apache Flex and Flash help or hinder the forked project’s future?
> 
> Please provide arguments in any direction.
> 
> (2) If a change is the outcome then we need to discuss and accumulate 
> reasonable names. Determine what is suitable by checking for other uses of 
> these names. If there are multiple choices available then we should vote.
> 
> A discussion of possible names can go in parallel to the discussion about 
> keeping FlexJS.
> 
> This discussion needs to proceed quickly if we want to have an open process 
> in advance of the next ASF Board meeting.
> 
> Regards,
> Dave

Re: [DISCUSS] Name of the FlexJS Fork

[Erik de Bruin]

For an Apache project, I think FlexJS would be the best name.

EdB



On Tue, Sep 12, 2017 at 10:45 AM, Olaf Krueger  wrote:

> I would stick with the name "FlexJS" for now.
> I do not think that people associate negative vibes with it.
> So many other JS frameworks are born every day, I think a new name may
> confuse people.
>
> But I agree that in future it could make sense to rename it, especially if
> there will be other targets than JS one day... who knows...
>
> Thanks,
> Olaf
>
>
>
>
>
>
> --
> Sent from: http://apache-flex-development.247.n4.nabble.com/
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [DISCUSS] Name of the FlexJS Fork

[Olaf Krueger]

I would stick with the name "FlexJS" for now.
I do not think that people associate negative vibes with it.
So many other JS frameworks are born every day, I think a new name may
confuse people.

But I agree that in future it could make sense to rename it, especially if
there will be other targets than JS one day... who knows...

Thanks,
Olaf






--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [DISCUSS] Name of the FlexJS Fork

[OmPrakash Muppirala]

I prefer a name change away from FlexJS.

I would like to concentrate more on getting new developers to the fold as
opposed concentrating on existing Flex developers.

The term FlexXX has a dated feel to it.  Maybe a new name will get folks to
check it out at which point they will feel like sticking to it.

Thanks,
Om

On Mon, Sep 11, 2017 at 11:20 PM, Alex Harui 
wrote:

> I would like some thoughts on a related question, but first some context:
>
> IMO, it would help to continue to develop and ship a product called Apache
> FlexJS right now to draw in migrating Flex folks.  And maybe some day,
> we'll ship a product that is more targeted to folks writing new JS apps
> and maybe even target runtimes other than JS, and that might have a name
> that doesn't have Flex in it.  So, the _project_ could be called something
> else, but it seems odd for there to be an Apache Flex project and an
> Apache XX project that ships an Apache FlexJS product.
>
> So my question is: How impactful the project name is compared to the
> product name?  I'm not sure I can recite the project/manufacturer names
> behind many products but most are the same at Apache.
>
> So, if someone thinks of a great project name that can encompass these
> possibilities in our future and Apache authorities won't object to using
> FlexJS for a product in a project with a different name, I would be in
> favor of the new name, but if project names aren't as impactful as product
> names, I'd just lean towards sticking with FlexJS as the project name for
> now just so we can get the proposal decided on in the September 20 board
> meeting and not have to wait more.
>
> Thoughts?
> -Alex
>
> On 9/11/17, 9:35 PM, "Piotr Zarzycki"  wrote:
>
> >Hi Dave,
> >
> >I believe that FlexJS is the right name. We have gained some recognition
> >and visibility among people and companies. I don't believe that we are
> >really at the beginning anymore.
> >
> >Our main first customers are companies who would like to rewrite their
> >apps
> >from Flex, so this connection is something really good.
> >If majority which response to this thread would like to change the name I
> >will not fight. Keep in mind that we really would like to have the project
> >split - I believe that is the most important to us.
> >
> >Thanks,
> >Piotr
> >
> >2017-09-12 3:01 GMT+02:00 Dave Fisher :
> >
> >> Hi -
> >>
> >> In discussions on the Board and Private list about the proposal voted
> >>on a
> >> few weeks ago to fork FlexJS it was pointed out that it would good to
> >> discuss if a new name should be attached to the forked project.
> >>
> >> There are one or two propositions to discuss.
> >>
> >> (1) FlexJS - is this distinct enough and will the historical connection
> >>to
> >> Adobe/Apache Flex and Flash help or hinder the forked project’s future?
> >>
> >> Please provide arguments in any direction.
> >>
> >> (2) If a change is the outcome then we need to discuss and accumulate
> >> reasonable names. Determine what is suitable by checking for other uses
> >>of
> >> these names. If there are multiple choices available then we should
> >>vote.
> >>
> >> A discussion of possible names can go in parallel to the discussion
> >>about
> >> keeping FlexJS.
> >>
> >> This discussion needs to proceed quickly if we want to have an open
> >> process in advance of the next ASF Board meeting.
> >>
> >> Regards,
> >> Dave
> >>
> >
> >
> >
> >--
> >
> >Piotr Zarzycki
> >
> >mobile: +48 880 859 557 <+48%20880%20859%20557>
> >skype: zarzycki10
> >
> >LinkedIn:
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.linked
> >in.com%2Fpiotrzarzycki=02%7C01%7C%7C9e4bacb6b08a4923de8108d4f997
> b9a7%
> >7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636407877434499520=
> Nhht
> >Kaf9RlzE9cCdJ3WErVGfHVFXsdQX%2BK48hw0Der8%3D=0
> > https%3A%2F%2Fpl.linke
> >din.com%2Fin%2Fpiotr-zarzycki-92a53552=02%
> 7C01%7C%7C9e4bacb6b08a4923d
> >e8108d4f997b9a7%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364078774344
> >99520=el1sClOn82J2rnnm4N01Te8Z5bPylMriHy%2Fdp0%2Budd0%3D=
> 0>
>
>

Re: [DISCUSS] Name of the FlexJS Fork

[Alex Harui]

I would like some thoughts on a related question, but first some context:

IMO, it would help to continue to develop and ship a product called Apache
FlexJS right now to draw in migrating Flex folks.  And maybe some day,
we'll ship a product that is more targeted to folks writing new JS apps
and maybe even target runtimes other than JS, and that might have a name
that doesn't have Flex in it.  So, the _project_ could be called something
else, but it seems odd for there to be an Apache Flex project and an
Apache XX project that ships an Apache FlexJS product.

So my question is: How impactful the project name is compared to the
product name?  I'm not sure I can recite the project/manufacturer names
behind many products but most are the same at Apache.

So, if someone thinks of a great project name that can encompass these
possibilities in our future and Apache authorities won't object to using
FlexJS for a product in a project with a different name, I would be in
favor of the new name, but if project names aren't as impactful as product
names, I'd just lean towards sticking with FlexJS as the project name for
now just so we can get the proposal decided on in the September 20 board
meeting and not have to wait more.

Thoughts?
-Alex

On 9/11/17, 9:35 PM, "Piotr Zarzycki"  wrote:

>Hi Dave,
>
>I believe that FlexJS is the right name. We have gained some recognition
>and visibility among people and companies. I don't believe that we are
>really at the beginning anymore.
>
>Our main first customers are companies who would like to rewrite their
>apps
>from Flex, so this connection is something really good.
>If majority which response to this thread would like to change the name I
>will not fight. Keep in mind that we really would like to have the project
>split - I believe that is the most important to us.
>
>Thanks,
>Piotr
>
>2017-09-12 3:01 GMT+02:00 Dave Fisher :
>
>> Hi -
>>
>> In discussions on the Board and Private list about the proposal voted
>>on a
>> few weeks ago to fork FlexJS it was pointed out that it would good to
>> discuss if a new name should be attached to the forked project.
>>
>> There are one or two propositions to discuss.
>>
>> (1) FlexJS - is this distinct enough and will the historical connection
>>to
>> Adobe/Apache Flex and Flash help or hinder the forked project’s future?
>>
>> Please provide arguments in any direction.
>>
>> (2) If a change is the outcome then we need to discuss and accumulate
>> reasonable names. Determine what is suitable by checking for other uses
>>of
>> these names. If there are multiple choices available then we should
>>vote.
>>
>> A discussion of possible names can go in parallel to the discussion
>>about
>> keeping FlexJS.
>>
>> This discussion needs to proceed quickly if we want to have an open
>> process in advance of the next ASF Board meeting.
>>
>> Regards,
>> Dave
>>
>
>
>
>-- 
>
>Piotr Zarzycki
>
>mobile: +48 880 859 557 <+48%20880%20859%20557>
>skype: zarzycki10
>
>LinkedIn: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linked
>in.com%2Fpiotrzarzycki=02%7C01%7C%7C9e4bacb6b08a4923de8108d4f997b9a7%
>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636407877434499520=Nhht
>Kaf9RlzE9cCdJ3WErVGfHVFXsdQX%2BK48hw0Der8%3D=0
>din.com%2Fin%2Fpiotr-zarzycki-92a53552=02%7C01%7C%7C9e4bacb6b08a4923d
>e8108d4f997b9a7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364078774344
>99520=el1sClOn82J2rnnm4N01Te8Z5bPylMriHy%2Fdp0%2Budd0%3D=0>