Carlos, Love your passion and share it fully. I cannot fully agree with you that having an old application in Flex people will need to rewrite completely. If they have separated enough good logic - they can put it without to much effort in our framework. - That is huge advantage in my opinion.
Voting is going well on renaming. We have enough voices. Even if I change my vote it is still pass with renaming. The question is - what's with code rename? Can we stay as is? - I think someone should start vote with all name proposition. I don't have capacity within next 24 hours. Piotr On Fri, Sep 15, 2017, 16:21 Carlos Rovira <carlos.rov...@codeoscopic.com> wrote: > Hi, > > I'm with Om and others that one of the results we pursue with this renaming > is to avoid the "Flex" name. We talked about the problems we have today > with clients when "Flex" is put in a discussion. You pay in terms of > credibility to your client. > > For migration : As a customer, I don't think migration is a real option. > FlexJS impose a very different code so almost all must be rewritten. You > only can think in maintain your languages (AS3/MXML) and environments (FB, > IDEA,...), so for me there's no much room there to discuss. I must say that > nowadays people like us considering to migrate would consider other actual > techs like Angular or React since the cost is similar and they get the > popular framework in 2017. > > I see this renaming as a way to rebrand all our project and present it to > the world with new visuals and marketing. And try to compete in the same > terms they do. Same kind of name, same kind of website, and so on... > > About Alex proposal to make different packages I think it could work, but > for me that would be a plan after rename, rebranding and website creation. > We can have it in mind for next steps after that. For me we need the same > top name for product and project, and then we can release a package for > people wanting to migrate called "apache XXX FlexJS" or something. But > consider that to make that real we will need people interested in make such > package and work for it. And consider how many people will be planing to > migrate from Flex and will find that FlexJS is completely different and > they can do it easily. > > @Piotr, my plans will be to work (if people wants me on that) on: website, > logo design.... for me the motivation to work in that things is to get a > name that will make me think we can reach our goals, since if I don't > believe in a name will be complicated to give us a good work. > Far beyond that I always want to put work on the visuals of a component > design, I think we need that as we need the website and new name. > > > > > > 2017-09-15 13:17 GMT+02:00 Kessler CTR Mark J <mark.kessler....@usmc.mil>: > > > I wanted to throw in a couple words / names to see if they "spark" > > anything. > > > > > > Arise > > Dawn > > Raise / Rise > > > > Dimension > > Facet > > Morph > > Poly > > Strand > > > > Derive > > Drive > > Quest > > Journey > > > > Fortune > > Prospect > > Trend > > > > > > -Mark K > > > > > > > -- > > <http://www.codeoscopic.com> > > Carlos Rovira > > Director General > > M: +34 607 22 60 05 > > http://www.codeoscopic.com > > http://www.avant2.es > > > Conocenos en 1 minuto! <https://youtu.be/P2IEAYDG5HU> > > > 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 nuestr > <https://maps.google.com/?q=rigi%C3%A9ndose+a+nuestr&entry=gmail&source=g> > as > oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación > necesaria. >
